bitbucket: 1.3 minutes to ask password, and 8 minutes to find out it is wrong ??
andy at vis.ethz.ch
Sun Jun 19 09:08:12 CDT 2011
On 19.06.2011 15:00, Mads Kiilerich wrote:
> rupert.thurner wrote, On 06/19/2011 01:19 PM:
>> when doing an initial push to an empty bitbucket or google mercurial
>> repository it takes nearly 10 minutes to get an "authorization
>> failed". only until mercurial asks the password one has to wait for
>> more than a minute.
> Obviously it works fine for everybody else. There must be something
> different between your setup and other setups. Please work
> systematically try to figure out what that could be - perhaps by trying
> to reproduce on another machine on another network connection - and
> perhaps another OS.
I did that just today and I can confirm that behavior. I moved a small
repository (~150 commits, thg transferred about 12 MiB data) to
BitBucket. When I pushed, the transfer started and it took a while (I
didn't use a stop watch, but I'd say it was a minute) before thg asked
for username and password. During this time the transfer was paused.
After I provided the information, the transfer resumed.
I can't say anything about "authorization failed", because I typed my
username and password correctly ;-)
Intel Core i7 (QuadCore) with 6 GiB RAM
Debian GNU/Linux unstable, Kernel 2.6.39
Mercurial: Mercurial Distributed SCM (version 1.8.3)
The computer is in a subnet behind the VDSL router (NAT) with a static
IP. The WAN (e.g. internet) IP of the router itself is also static.
IMHO: I doubt that this is a Mercurial problem, I suspect the BitBuckt
`o_ o ) `-. ( ).`-.__.`)
(_Y_.)' ._ ) `._ `. ``-..-'
_..`--'_..-_/ /--'_.' .'
(il).-'' (li).' ((!.-'
Andreas Tscharner andy at vis.ethz.ch ICQ-No. 14356454
More information about the Mercurial