Community
Participate
Working Groups
Sorry in advance for the lack of detail on this bug. With the recent Orion workspace wipe, I've been cloning a lot of repos the last couple of days. It never seems to work the first time, I get error 500's and the error says: invalid remote: origin This happened with both the Orion client workspace and one of my github repos. I tried a handful of times and eventually it worked. It is "possible" that it worked once I had forced a reload of the page, or that could have been coincidence. Hoping that the "invalid remote: origin" might be a clue to the problem.
Created attachment 209635 [details] screenshot showing failures I doubt this is helpful, but oh well. I captured this popup while reporting a different bug. It shows all the failed attempts (there are some other errors mixed in).
(In reply to comment #0) > Hoping that the "invalid remote: origin" might be a clue to the problem. It definitely is. This message accompanies 500 error when the URI you entered is either malformed or doesn't point to an existing repo. Since you kept banging with the same URI and it eventually worked I assume it was a connectivity error. I guess a country girl like you is on a mobile broadband rather than hard wired connection ;) May that be a factor? See also org.eclipse.orion.server.tests.servlets.git.GitCloneTest.testCloneNotGitRepository() when we have assertions on this kind of message when trying to clone a regular folder, not a git repo.
(In reply to comment #2) > (In reply to comment #0) > > Hoping that the "invalid remote: origin" might be a clue to the problem. > > It definitely is. This message accompanies 500 error when the URI you entered > is either malformed or doesn't point to an existing repo. Since you kept > banging with the same URI and it eventually worked I assume it was a > connectivity error. I guess a country girl like you is on a mobile broadband > rather than hard wired connection ;) May that be a factor? Not mobile broadband but sometimes flaky. We also had a lot of power glitches in a recent ice storm and this may have been during that time.
Could be. I'm marking it as WORKSFORME, but feel free to reopen if you see those failures again.
