From 403acdb8efdd19024ef3be14bde755a5729cda6d Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 11 Sep 2026 18:02:31 +0000 Subject: [PATCH] docs: say what the download services do, not what one did once The comment beside CURL_RETRY dates an outage. What the retries are for is that the service in front of the bytes answers 429 under load and sometimes nothing at all, which is true on any day. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_019ghEx26MRm9V5CnCLrdUQn --- Dockerfile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Dockerfile b/Dockerfile index 28c297daf..3e454eaf5 100644 --- a/Dockerfile +++ b/Dockerfile @@ -27,9 +27,9 @@ RUN apk add --no-cache gmp \ # Fetched before wikven's own code is copied in, so an edit there does not bust the slow layers. -# "Stable source" describes the bytes, not the service in front of them: GitHub served 500s for -# hours on 2026-08-17, and codeload answers 429 under load. --retry-all-errors as well as --retry, -# because curl counts a connection reset as non-transient and would not repeat it. +# "Stable source" describes the bytes, not the service in front of them, which answers 429 under +# load and sometimes nothing at all. --retry-all-errors as well as --retry, because curl counts a +# connection reset as non-transient and would not repeat it. ARG CURL_RETRY="--retry 5 --retry-delay 2 --retry-all-errors" # And who is asking: curl signs with its own version, naming the library rather than the project.