On Mon, 24 Sep 2018 07:59:46 +0200 Michał Górny <mgo...@gentoo.org> wrote:
> I'm against dumb timeouts. Good timeout = die if nothing happens for T. > Bad timeout = die if process doesn't finish for T (yet it may still be > doing something). Could you perhaps adjust it so that when the timeout limit is exceeded, the sync is aborted, and the sync status of that repository is flagged as "bad", and notifies you somehow to fix it manually at your leisure, but otherwise ceases to impede the progress of all the other repositories? And if you're worried that a sync interruption midway could cause a dirty state, maybe you could do an rsync trick where mercurial repos are rsynced into a sandbox location, and then only rsynced back into place on success? This process lets you go "sure, it may be doing something, but it took too long anyway, so we'll let somebody with brains work it out and pretend it was broken in the interim"
pgpnNslW9HK50.pgp
Description: OpenPGP digital signature
