| 1 |
On 2018-10-04 18:05, Cédric Krier wrote: |
| 2 |
> On 2018-09-29 11:42, Cédric Krier wrote: |
| 3 |
> > On 2018-09-23 22:42, Michał Górny wrote: |
| 4 |
> > > Yes, I could add process timeouts. But small timeouts are going to |
| 5 |
> > > break the occasional necessity of cloning big repos, and big timeouts |
| 6 |
> > > are going to make little difference when Mercurial starts hanging again. |
| 7 |
> > > |
| 8 |
> > > If someone really cares about this horrible piece of software, I'd |
| 9 |
> > > appreciate patches (preferably going upstream) to make it timeout sanely |
| 10 |
> > > when something hangs. Otherwise, I'd like to announce discontinuation |
| 11 |
> > > of Mercurial support soon. |
| 12 |
> > |
| 13 |
> > FYI, I send an email to mercurial list to talk about this issue [1]. And it |
| 14 |
> > seems that for HTTP connections there is no timeout on the connection. |
| 15 |
> > I'm working to provide to the upstream a solution to be able to |
| 16 |
> > configure a timeout. |
| 17 |
> |
| 18 |
> Normally, the feature should be available for the next release of |
| 19 |
> mercurial: https://phab.mercurial-scm.org/D4878 |
| 20 |
|
| 21 |
For the record, the feature is now in the release 4.8 of Mercurial: |
| 22 |
https://www.mercurial-scm.org/wiki/Release4.8 |
| 23 |
|
| 24 |
-- |
| 25 |
Cédric Krier |
Archives