Closed Bug 688636 Opened 15 years ago Closed 14 years ago

ssh hg.mozilla.org clone interactive iface does not provide option to choose public repo for cloning

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: romaxa, Assigned: rtucker)

References

Details

ssh hg.mozilla.org clone mozilla-release-8.0 Making repo mozilla-release-8.0 for romaxa@gmail.com. This repo will appear as hg.mozilla.org/users/romaxa_gmail.com/mozilla-release-8.0. If you need a top level repo, please quit now and file a bug for IT to create one for you. 0) Exit. 1) yes. 2) no. Proceed? 1 You can clone an existing public repo or a users private repo. You can also create an empty repository. 0) Exit. 1) Clone a public repository. 2) Clone a private repository. 3) Create an empty repository. Source repository: 1 About to create an empty repository at /users/romaxa_gmail.com/mozilla-release-8.0 0) Exit. 1) yes. 2) no.
What happens when you select 1 at the last prompt?
Assignee: server-ops → shyam
(In reply to Shyam Mani [:fox2mike] from comment #1) > What happens when you select 1 at the last prompt? you get an empty repository. which you can then pull m-c to and push to your user repo (without merging or updating), so there's a workaround.
pushing mozilla-repo clone into that repo, will take ages, and in 95% cases fail with timeout :(
(In reply to Shyam Mani [:fox2mike] from comment #1) > What happens when you select 1 at the last prompt? Nothing, empty repo created, and I need to do manual pull/push which endup with problem in comment 3
I'm in the same boat, except I don't get timeouts, I get HTTP 413 since the request is enormous: abort: HTTP Error 413: Request Entity Too Large Is there another way to clone a large database other than pull/push?
I received the error message in comment 5 by trying to push to a repo without ssl (sorry, my mistake), so you can discard the above comment. I was able to push the cloned repo without a timeout.
I just ran into the same problem. I can't clone a public repository into a user repository. This was filed a month ago. This is a critical part of our work flow? Can we please fix it? maui:~ gal$ ssh "agal@mozilla.com"@hg.mozilla.org clone ieframe Making repo ieframe for agal@mozilla.com. This repo will appear as hg.mozilla.org/users/agal_mozilla.com/ieframe. If you need a top level repo, please quit now and file a bug for IT to create one for you. 0) Exit. 1) yes. 2) no. Proceed? 1 You can clone an existing public repo or a users private repo. You can also create an empty repository. 0) Exit. 1) Clone a public repository. 2) Clone a private repository. 3) Create an empty repository. Source repository: 1 About to create an empty repository at /users/agal_mozilla.com/ieframe 0) Exit. 1) yes. 2) no. Proceed? 2 Fixing permissions, don't interrupt. maui:~ gal$ ssh "agal@mozilla.com"@hg.mozilla.org clone ieframe Making repo ieframe for agal@mozilla.com. This repo will appear as hg.mozilla.org/users/agal_mozilla.com/ieframe. If you need a top level repo, please quit now and file a bug for IT to create one for you. 0) Exit. 1) yes. 2) no. Proceed? 1 You can clone an existing public repo or a users private repo. You can also create an empty repository. 0) Exit. 1) Clone a public repository. 2) Clone a private repository. 3) Create an empty repository. Source repository: 1 About to create an empty repository at /users/agal_mozilla.com/ieframe 0) Exit. 1) yes. 2) no. Proceed? 1 Fixing permissions, don't interrupt.
this feature (albeit a broken one) is a custom, undocumented hack that someone put on our hg infrastructure long ago. We are looking for it to try and figure it out and fix it but this is going to take some time. in the meantime, thanks for your patience.
Here's a workaround (from what we use for doing test releases in RelEng): ssh hg.mozilla.org clone <destination> <source> eg comment #0 becomes ssh hg.mozilla.org clone mozilla-release-8.0 releases/mozilla-release
Assignee: shyam → rtucker
After digging through the code and talking with fox2mike, it appears as though the proper usage is what nthomas describes. Do we have more usage examples that we are 100% confident used to work but no longer do? ssh "agal@mozilla.com"@hg.mozilla.org clone ieframe creates an empty repository because a source repo to hg clone is not known.
(In reply to Rob Tucker [:rtucker] from comment #11) > After digging through the code and talking with fox2mike, it appears as > though the proper usage is what nthomas describes. > > Do we have more usage examples that we are 100% confident used to work but > no longer do? > > ssh "agal@mozilla.com"@hg.mozilla.org clone ieframe creates an empty > repository because a source repo to hg clone is not known. https://developer.mozilla.org/en/Creating_Mercurial_User_Repositories#Creating_a_Repository tells people to use the ssh hg.mozilla.org clone <new repo> syntax and says they will end up encountering the interactive script that will allow them to select what repo to clone.
Ian, Great I'll start there To confirm: The expected action is that after: You can clone an existing public repo or a users private repo. You can also create an empty repository. 0) Exit. 1) Clone a public repository. 2) Clone a private repository. 3) Create an empty repository. Source repository: 1 It should give you a list of available repositories and you can then select the repo that you want to clone from the list, and then it will get cloned the same way it does with this syntax: ssh hg.mozilla.org clone mozilla-release-8.0 releases/mozilla-release
(In reply to Rob Tucker [:rtucker] from comment #13) > To confirm: > The expected action is that after: > You can clone an existing public repo or a users private repo. > You can also create an empty repository. > It should give you a list of available repositories and you can then select > the repo that you want to clone from the list, and then it will get cloned > the same way it does with this syntax: > > ssh hg.mozilla.org clone mozilla-release-8.0 releases/mozilla-release that's certainly what i was expecting :) although i haven't seen it work since i tried making a user repo for the first time after it was no longer working.
Can you please take a look again. I never used this previously, so I don't really have a baseline to compare to, but I *think* I've fixed this. If you could confirm that would be great!
(In reply to Rob Tucker [:rtucker] from comment #15) > Can you please take a look again. I never used this previously, so I don't > really have a baseline to compare to, but I *think* I've fixed this. If you > could confirm that would be great! i got the interactive menu this time and picked mozilla-central. it's still cloning but it looks like it's working, will update when/if it finishes successfully.
Ian(In reply to Ian Melven :imelven from comment #16) > (In reply to Rob Tucker [:rtucker] from comment #15) > > Can you please take a look again. I never used this previously, so I don't > > really have a baseline to compare to, but I *think* I've fixed this. If you > > could confirm that would be great! > > i got the interactive menu this time and picked mozilla-central. it's still > cloning but it looks like it's working, will update when/if it finishes > successfully. I picked a repo called penelope which cloned really quickly and is now visible here: http://hg.mozilla.org/users/rtucker_mozilla.com/ I believe it is the expected behavior
mine finally finished but timed out Pick a source repo: 3 About to clone /mozilla-central to /users/imelven_mozilla.com/iframe_sandbox 0) Exit. 1) yes. 2) no. Proceed? 1 Please do not interrupt this operation. Please wait. Cloning /mozilla-central to /users/imelven_mozilla.com/iframe_sand box Read from remote host hg.mozilla.org: Connection reset by peer but the repo is there and superficially looks ok. thanks for fixing this up :)
Am I ok to Resolve/Fix this one?
I'm gonna go ahead and R/F this. Please feel free to reopen if you see any more issues with this. Thanks.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.