feat(cdn): enable per-R-minor routing in production #184
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/enable-union-slots"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
Everything built today is unreachable until this is set.
No
4.6/in that path. WithUNION_SLOTSempty the client resolves against the generic index and never reaches a per-minor binary:4.6/, R 4.6-builtThe working binary has existed since 12:13 today. Nothing routes anyone to it.
Change
Sets production
UNION_SLOTSto all 16 slots, from the samelocal.rpkgs_slotsthe staging zone uses.Verified before enabling
Against the staging zone, which runs the identical script against the identical origin:
Trade-off, stated plainly
Coverage on a non-primary minor drops where the per-minor build backlog has not been worked off.
amd64/resoluteserves a 4.6 client 22169 packages rather than the generic slot's 24310.Those ~2100 are ABI-risky packages built under another R minor. They are exactly the ones that would install and then fail at load, so the drop trades a confusing runtime crash for an honest "not available". It shrinks as the 4.6 builds land.
If that trade is unwelcome for some slots,
local.rpkgs_slotscan be narrowed to a subset —amd64/rhel10andamd64/alpine323have the smallest backlogs — and widened as builds catch up.After applying
and the reported case directly: