| 1 |
On 09/27/18 10:21, Michał Górny wrote: |
| 2 |
> On Fri, 2018-09-28 at 01:50 +1200, Kent Fredric wrote: |
| 3 |
>> On Mon, 24 Sep 2018 07:59:46 +0200 |
| 4 |
>> Michał Górny <mgorny@g.o> wrote: |
| 5 |
>> |
| 6 |
>>> I'm against dumb timeouts. Good timeout = die if nothing happens for T. |
| 7 |
>>> Bad timeout = die if process doesn't finish for T (yet it may still be |
| 8 |
>>> doing something). |
| 9 |
>> |
| 10 |
>> Could you perhaps adjust it so that when the timeout limit is exceeded, |
| 11 |
>> the sync is aborted, and the sync status of that repository is flagged |
| 12 |
>> as "bad", and notifies you somehow to fix it manually at your leisure, |
| 13 |
>> but otherwise ceases to impede the progress of all the other |
| 14 |
>> repositories? |
| 15 |
>> |
| 16 |
>> And if you're worried that a sync interruption midway could cause a |
| 17 |
>> dirty state, maybe you could do an rsync trick where mercurial repos |
| 18 |
>> are rsynced into a sandbox location, and then only rsynced back into |
| 19 |
>> place on success? |
| 20 |
>> |
| 21 |
>> This process lets you go "sure, it may be doing something, but it took |
| 22 |
>> too long anyway, so we'll let somebody with brains work it out and |
| 23 |
>> pretend it was broken in the interim" |
| 24 |
> |
| 25 |
> No. |
| 26 |
> |
| 27 |
Elucidate. |
Archives