refactor(oci): consume dunite-oci shared limiter API and typed blob-cache errors (PSA-35) #38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refactor/psa-35-dunite-oci-consumer"
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?
What
Consumer-side update for the dunite-oci API changes merged in dunite PR #4 (PSA-35). Mechanical changes only; registry behavior improves where errors were previously flattened.
UsageCounter(nocurrent()); the repository's trait impl drops it, the inherentcurrent()method stays for tests/diagnostics.BlobCacheErrorvia dunite-oci'sFrom<&BlobCacheError> for OciError(spec classification lives next to the types); the handler keeps only Bunyip's logging and audit policy. Forgejo transport failures now return 502 with an upstream-cause log, filesystem failures return 500 with the real cause; previously everything non-404 was a generic 502 with a flattened string (the BUNYIP-31 finding).269ee30.Verification
Run in the rust-builder container with the pinned 1.93.0 toolchain:
cargo test -p bunyip-oci --lib: 7 passed, 0 failedcargo check -p bunyip-api --all-targets: cleancargo test --workspace --lib: all greencargo fmt -p bunyip-oci --check: cleancargo clippy -p bunyip-oci --no-deps: no new violations; the 4 pre-existing ones (untouched files/lines) plus the bunyip-domain violations are tracked in BUNYIP-36Note on CI
The repo's check workflow currently fails on main (pre-existing fmt/clippy violations, BUNYIP-36), so the check on this PR will be red for the same pre-existing reasons, not because of this change.