fix(abi): enumerate the flat slot from S3, not through the edge #203
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/flat-safety-enumeration"
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?
Why
The first backfill run reported:
292 of 300 skipped, and
27105is larger than the flat index (~24k). Both have the same cause: the script readPACKAGES.gzover HTTPS from inside R, which sends an R User-Agent, so the edge routed it to a per-minor index. It then enumerated union records carryingPath: <minor>, whose objects do not exist at the flat path, and every download 404'd.An ironic failure given what this whole change is about, and one the trial run existed to catch.
What changed
s3fs::s3_dir_ls(), keeping only objects with no<minor>/prefix and nothing underArchive/. The bucket cannot be routed and is authoritative about what is actually in the flat slot.NeedsCompilationstill comes from CRAN's own index, which is not behind our edge.Verification
The next trial run is the check:
flat objectsshould now match the flat index rather than exceed it, andskippedshould be near zero.bd0003dfdbto1c1b242dc6