RanaPriyansh opened a new pull request, #873: URL: https://github.com/apache/arrow-rs-object-store/pull/873
# Which issue does this PR close? Related to #760. This PR covers external-provider integration tests. # Rationale for this change Existing provider tests do not show that an external implementation works through the public object_store client API. # What changes are included in this PR? Add a separate downstream test crate with an external Ring provider and an in-memory HTTP connector. Capture a signed PUT through the public AWS client and compare its signature with independent Ring operations. Check digest and HMAC failure propagation, custom-provider selection, bundled-provider fallback, and `aws-base` without a provider. Add CI commands for the separate crate. The fixture makes no cloud requests. Validation on Ubuntu 24.04 with Rust 1.97.0: - All 15 provider cases pass across three configurations. - Root default tests pass 135 cases, with three ignored. - Root Ring tests pass 271 cases, with six ignored. - All three fixture and eight root Clippy commands pass with warnings denied. - Formatting, current spelling, and source/lock integrity checks pass. The [first job](https://github.com/RanaPriyansh/arrow-rs-object-store/actions/runs/37794749507) passed tests and Clippy but failed spelling with typos 1.37.0 on four unchanged identifiers. The [continuation](https://github.com/RanaPriyansh/arrow-rs-object-store/actions/runs/37797759761) passed formatting, typos 1.51.1, and source/lock integrity. Its additional dependency audit failed because Cargo's [CLI feature resolution](https://github.com/rust-lang/cargo/blob/c980f4866/src/cargo/ops/resolve.rs#L226-L236) adds nine TLS packages outside the persisted workspace lock. Their recorded versions match the first job's compilation log. Both job failures remain visible. # Are there any user-facing changes? No public API changes. Codex used. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
