Weird push problem

[Scott Palmer]

On 2011-08-12, at 5:18 PM, Mads Kiilerich wrote:

> On 08/12/2011 10:54 PM, Scott Palmer wrote:
>> I'm trying to push changes to a repo I'm serving up with hgweb…  I haven't booted up the server I'm pushing to in a while, but it was working fine the last time I tried… the thing that would be different is that now I'm pushing from a more recent client version.
>> 
>> hg push
>> pushing to http://private_repo_URL_here/
>> searching for changes
>> 
>> .. does NOT ask for authorization - this is expected, it should be cache with mercurial_keyring.
>> .. now "sending" progress bar counts out to 12526
>> .. after that phase  is complete it suddenly asks for a password:
> 
> ...
> 
>> $ hg --version
>> Mercurial Distributed SCM (version 1.9.1+2-9991f8b19ff3)
>> (see http://mercurial.selenic.com for more information)
> 
> Patrick has made some important fixes in this area since 1.9.1 - see http://mercurial.selenic.com/bts/issue2885 . Please try again with the tip of the stable branch. It will probably either fix your issues or at least make them look different ;-)
> 
> He also made some fixes for keyring - make sure you also have these.
> 
> /Mads


Okay the crash was just not having the latest keyring, like you mention above…

I changed the hgrc file so there would be no matching username for the domain… I was hoping that would avoid the mercurial_keyring path.  It obviously wasn't enough.
Now I've just disabled the keyring extension to try again… (easier at the moment than figuring out how to get the latest code running)

While it doesn't keep asking for a password.. it does continue past the 100% point on the progress bar and the time remaining goes negative again…

sending [                              <=>                  ] 14510/12526 -123s
...
sending [                        <=>                       ] 29212/12526 -1032s
… and eventually fails…
sending [                 <=>                              ] 43841/12526 -1972sabort: authorization failed


Scott