{"version":"2.1.227","anchor":"slow-git-fetches-are-recognised-as-timeouts-not-server-error","canonical_anchor":"slow-git-fetches-are-recognised-as-timeouts-not-server-error","heading":"Slow git fetches are recognised as timeouts, not server errors","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/slow-git-fetches-are-recognised-as-timeouts-not-server-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Slow git fetches are recognised as timeouts, not server errors\n\nA stalled git fetch is now reported as a timeout, not a remote server failure.\n\n**What**\n\nA git fetch that stalls locally is now correctly reported as a transfer timeout rather than a remote failure.\n\n**Details**\n\n- Fetch error output is scanned line by line for `Operation too slow`, and attributed to a local curl exit 28 timeout only when that line is not prefixed as a message from the remote.\n- Fetch telemetry gained extra per-attempt fields.\n\n**Evidence**\n\n`Operation too slow`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}