"hg push" hangs for one minute (exactly one minute)

[Scott Palmer]

This is interesting to me.  I have a similar issue with pushes to a repo hosted on a Linux server that uses a NAS for the repo storage. 

In fact I noticed that the changeset I push is available to pull well before the push returns.  I think I observed a 30 second delay, but clearly a nice round number that hinted to me that it was really just a timeout of some sort.

I recall that during some experiments I found that it may be related to having the evolve extension enabled.

Scott

> On Apr 27, 2022, at 7:36 AM, Ernie Rael <err at raelity.com> wrote:
> 
> I've recently moved from a windows machine to a new linux laptop. I've got an ancient NAS which I use from both windows and linux; everything's been good; read/write from linux and windows to the NAS OK.
> 
> I finally got around to doing a mercurial push to the NAS from linux today. It took a long time; it finally finished. I did another push, it quickly prints "no changes found", and then sits there for one minute and finally finishes. Windows native hg push to the NAS is as expected.
> 
> An hg push to a local filesystem doesn't pause.
> 
> Any idea how to track this down? Where's the timer? How to make it happy?
> 
>    $ hg --version -v
>    Mercurial Distributed SCM (version 6.1)
> 
>    $ time hg push
>    pushing to /z/repos/jvi-dev/jvi
>    searching for changes
>    no changes found
> 
>    real    1m0.761s
>    user    0m0.210s
>    sys    0m0.054s
> 
> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial