Mercurial push locks

[durwin at mgtsciences.com]

Matt Mackall <mpm at selenic.com> wrote on 09/26/2014 03:30:00 PM:

> From: Matt Mackall <mpm at selenic.com>
> To: durwin at mgtsciences.com, 
> Cc: Mercurial mailing list <mercurial at selenic.com>, Simon King 
> <simon at simonking.org.uk>
> Date: 09/26/2014 03:30 PM
> Subject: Re: Mercurial push locks
> 
> On Fri, 2014-09-26 at 11:19 -0600, durwin at mgtsciences.com wrote:
> > > > > With the introduction of phases (Mercurial 2.1, Feb 2012), 
pushes 
> > may
> > > > > now acquire a lock on the sending side (so that it can update 
the 
> > phase
> > > > > of local commits). Thus, you may get a deadlock if you push 
inside a
> > > > > hook where a lock is already held.
> > > > 
> > > > This appears to what is occurring.  Is there a way around this?  I 

> > need to 
> > > > perform a push
> > > > to the other repository after each push to either.  Should I 
change 
> > this 
> > > > to a script and
> > > > run it in an 'at' job delayed a minute?
> > > 
> > > What version of Mercurial are you running on the server?
> > 
> > Mercurial version 2.6.3
> 
> Hmmm, shouldn't be a problem here: the changegroup hook is run
> immediately after lock release.
> 
> Perhaps you can create a minimal model of your flow:
> 
> $ hg init local
> $ hg init server1
> # add push hook
> $ hg init server2
> 
> ..and see if you can get it to lock.

I do have a 'test' repository where all I have are two files.  The hook 
always works for me.  In fact the project repository all ways works for 
me.  There was a time where I would see the lock, but that is no longer 
occurring.  I tried logging into server as one of the users having the 
problem and cloned their repository, but it would not lock up, it pushed 
just fine.

Thank you
> 
> -- 
> Mathematics is the supreme nostalgia of our time.
> 
> 



This email message and any attachments are for the sole use of the 
intended recipient(s) and may contain proprietary and/or confidential 
information which may be privileged or otherwise protected from 
disclosure. Any unauthorized review, use, disclosure or distribution is 
prohibited. If you are not the intended recipient(s), please contact the 
sender by reply email and destroy the original message and any copies of 
the message as well as any attachments to the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20140926/c4be0de9/attachment-0002.html>