Lstarsky0 opened a new issue, #10757: URL: https://github.com/apache/arrow-rs/issues/10757
`arrow-pyarrow` never gets a clippy run. Of the 25 published crates in the workspace it is the only one: the other 24 are covered by `arrow.yml`'s clippy job or by the per-crate jobs in `arrow_flight.yml`, `parquet.yml` and `parquet_derive.yml`. The only other workspace members with no clippy are `gen` and `parquet_derive_test`, both `publish = false`. #10724 closed the same gap for `arrow-cmp`, so this reads as the remainder of that rather than a deliberate exclusion. It can't simply be appended to `arrow.yml`'s clippy job, which is where the other `arrow-*` crates are linted — that job runs in the `amd64/rust` container and pyo3 needs an interpreter to link against. The `Pyarrow C Data Interface` job in `integration.yml` already sets one up, and its toolchain step already runs `rustup component add rustfmt clippy` without ever calling clippy. Nothing is wrong with the crate today — it passes both `cargo clippy -p arrow-pyarrow --all-targets --all-features -- -D warnings` and the `-D unused_crate_dependencies` check. This is only about keeping it that way. -- 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]
