alamb opened a new pull request, #11727:
URL: https://github.com/apache/arrow-rs/pull/11727
# Which issue does this PR close?
- Part of #11665 (58.4.1 release)
# Rationale for this change
CI is red on every PR against `58_maintenance` (for example #11365, #11703,
#11704, #11705, #11707) for reasons unrelated to those PRs. Four jobs fail on
the branch itself:
1. **Verify MSRV**: `uuid` 1.27.0 and newer require Rust 1.89, above the
branch MSRV of 1.85. We do not commit a `Cargo.lock` on this branch, so `cargo
msrv verify` resolves fresh and picks the newest `uuid`.
2. **Rustdocs are clean**: the current nightly rustdoc reports `redundant
explicit link target` in `arrow-avro`, which fails under `-Dwarnings`.
3. **MIRI**: `datatype_parse::test::parse_data_type_errors` asserts on the
exact `TryFromIntError` message, which changed on nightly ("number too large to
fit in target type").
4. **Archery test With other arrows**: the upstream integration test suite
now generates `list_view`, `binary_view` and `run_end_encoded` cases, which the
integration test JSON parser on this branch does not understand.
The clippy failure on #11365 is separate: the new tests in that PR use the
deprecated `format::Statistics` type without `#[allow(deprecated)]`, so it
needs a fix in that PR.
# What changes are included in this PR?
- Check in the root `Cargo.lock` (generated with Rust 1.85 using the
MSRV-aware resolver, so it pins `tonic` to 0.14.5 and `uuid` to 1.26.1), the
same approach as https://github.com/apache/arrow-rs/pull/9941 ("Fix MSRV check
by checking in Cargo.lock") on `main`. The manual "Downgrade workspace
dependencies" step in the MSRV workflow is removed since the lockfile now
covers it.
- Backport #11305 (via the `59_maintenance` port #11354): remove duplicate
`homepage` entries and let rustdoc infer the targets of five `arrow-avro`
intra-doc links.
- Backport #10433: stop asserting on the unstable `TryFromIntError` message
in the `arrow-schema` tests.
- Backport #9888: support `ListView`, `BinaryView` and `RunEndEncoded` in
the integration test JSON parser.
# Are these changes tested?
- `cargo +1.85.0 check --workspace --locked` passes with the committed
lockfile.
- `cargo test -p arrow-integration-test` and `cargo test -p arrow-schema
--lib parse_data_type_errors` pass.
- `cargo clippy -p arrow-integration-test -p arrow-schema --all-targets
--all-features -- -D warnings` and `cargo fmt --check` pass.
- The rustdoc change matches what already passes on `main` and
`59_maintenance`; CI will confirm with the current nightly.
# Are there any user-facing changes?
No.
--
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]
