Skip to main content

max / alloy

Move QUASI_TYPE_REV to the revision that retries a fetch The image asks raw.githubusercontent.com for the pinned bases four times per build - two slots here, one more in shop's build script - and that is enough to be rate-limited. `build/check-rust-stage.sh` failed on a 429 from the licence fetch with the bytes one second away, so quasi-type's fetch now retries. It bounds the damage rather than fixing the cause. The cause is four fetches leaving the machine at all, and the answer is a mirror on infrastructure we own, which is the same conversation as ebf30337 (the Fedora base images) and is filed as 3d41d15a.
Author: Max Johnson <me@maxj.phd> · 2026-08-17 15:45 UTC
Signed with PGP, not checked
Commit: 2b4109cb4ffe07e3bc66eb92e4f434139b4e33da
Parent: 6a91094
1 file changed, +1 insertion, -1 deletion
M Containerfile +1 -1
@@ -225,7 +225,7 @@
225 225 #
226 226 # Above the console's source for the same reason shop is: keyed on a revision
227 227 # that changes rarely, so a console edit does not recut two fonts.
228 - ARG QUASI_TYPE_REV=6d076b7f85268381f6cd34dd0d28e84c574929cc
228 + ARG QUASI_TYPE_REV=cbbb9e3dd6faa29582b9437c0685ff91af97afdb
229 229 RUN git clone --no-checkout https://makenot.work/git/max/quasi-type.git /quasi-type && \
230 230 git -C /quasi-type checkout --detach "${QUASI_TYPE_REV}" && \
231 231 cargo build --release --locked --manifest-path /quasi-type/Cargo.toml && \