Re: RFC: Would a config fetch.retryCount make sense?

2017-06-05 Thread Ben Peart
On 6/5/2017 8:04 AM, Lars Schneider wrote: On 01 Jun 2017, at 15:33, Ben Peart wrote: On 6/1/2017 8:48 AM, Lars Schneider wrote: Hi, we occasionally see "The remote end hung up unexpectedly" (pkt-line.c:265) on our `git fetch` calls (most noticeably in our automations). I expect random n

Re: RFC: Would a config fetch.retryCount make sense?

2017-06-05 Thread Lars Schneider
> On 01 Jun 2017, at 15:33, Ben Peart wrote: > > > > On 6/1/2017 8:48 AM, Lars Schneider wrote: >> Hi, >> we occasionally see "The remote end hung up unexpectedly" (pkt-line.c:265) >> on our `git fetch` calls (most noticeably in our automations). I expect >> random network glitches to be the c

Re: RFC: Would a config fetch.retryCount make sense?

2017-06-01 Thread Stefan Beller
On Thu, Jun 1, 2017 at 5:48 AM, Lars Schneider wrote: > Hi, > > we occasionally see "The remote end hung up unexpectedly" (pkt-line.c:265) > on our `git fetch` calls (most noticeably in our automations). I expect > random network glitches to be the cause. There is 665b35eccd (submodule--helper: i

Re: RFC: Would a config fetch.retryCount make sense?

2017-06-01 Thread Ben Peart
On 6/1/2017 8:48 AM, Lars Schneider wrote: Hi, we occasionally see "The remote end hung up unexpectedly" (pkt-line.c:265) on our `git fetch` calls (most noticeably in our automations). I expect random network glitches to be the cause. In some places we added a basic retry mechanism and I was

RFC: Would a config fetch.retryCount make sense?

2017-06-01 Thread Lars Schneider
Hi, we occasionally see "The remote end hung up unexpectedly" (pkt-line.c:265) on our `git fetch` calls (most noticeably in our automations). I expect random network glitches to be the cause. In some places we added a basic retry mechanism and I was wondering if this could be a useful feature f