-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.15 not compatible with 1.63 despite rust-version
hint
#574
Comments
That ordering restriction was removed by rust-lang/rust#98383 in Rust 1.64. So yes, the default hasher from |
Ah, makes sense. I hadn't considered the feature combination 👍 Thanks for clarifying that. I think let's close this given the MSRV testing seems to be incoming in #572 |
- eyre: 0.4 => 0.6.8 - hashbrown: 0.9 => 0.14.5 - indexmap: 1.6 => 2.5.0 - num-complex: 0.2 => 0.4.6 - chrono-tz: 0.10 => 0.11 Eyre is limited to 0.6.8 to be compatible with MSRV 1.63 Hashbrown limited to 0.14.5: rust-lang/hashbrown#574 Indexmap is limited to 2.5.0 to be compatible with hashbrown 0.14.5
- eyre: 0.4 => 0.6.8 - hashbrown: 0.9 => 0.14.5 - indexmap: 1.6 => 2.5.0 - num-complex: 0.2 => 0.4.6 - chrono-tz: 0.10 => 0.11 Eyre is limited to 0.6.8 to be compatible with MSRV 1.63 Hashbrown limited to 0.14.5: rust-lang/hashbrown#574 Indexmap is limited to 2.5.0 to be compatible with hashbrown 0.14.5
- eyre: 0.4 => 0.6.8 - hashbrown: 0.9 => 0.14.5 - indexmap: 1.6 => 2.5.0 - num-complex: 0.2 => 0.4.6 - chrono-tz: 0.10 => 0.11 Eyre is limited to 0.6.8 to be compatible with MSRV 1.63 Hashbrown limited to 0.14.5: rust-lang/hashbrown#574 Indexmap is limited to 2.5.0 to be compatible with hashbrown 0.14.5
- eyre: 0.4 => 0.6.8 - hashbrown: 0.9 => 0.14.5 - indexmap: 1.6 => 2.5.0 - num-complex: 0.2 => 0.4.6 - chrono-tz: 0.10 => 0.11 Eyre min-version is limited to 0.6.8 to be compatible with MSRV 1.63 Hashbrown min-version is limited to 0.14.5: rust-lang/hashbrown#574 Indexmap min-version is limited to 2.5.0 to be compatible with hashbrown 0.14.5
- eyre: 0.4 => 0.6.8 - hashbrown: 0.9 => 0.14.5 - indexmap: 1.6 => 2.5.0 - num-complex: 0.2 => 0.4.6 - chrono-tz: 0.10 => 0.11 Eyre min-version is limited to 0.6.8 to be compatible with MSRV 1.63 Hashbrown min-version is limited to 0.14.5: rust-lang/hashbrown#574 Indexmap min-version is limited to 2.5.0 to be compatible with hashbrown 0.14.5
- eyre: 0.4 => 0.6.8 - hashbrown: 0.9 => 0.14.5 - indexmap: 1.6 => 2.5.0 - num-complex: 0.2 => 0.4.6 - chrono-tz: 0.10 => 0.11 Eyre min-version is limited to 0.6.8 to be compatible with MSRV 1.63 Hashbrown min-version is limited to 0.14.5: rust-lang/hashbrown#574 Indexmap min-version is limited to 2.5.0 to be compatible with hashbrown 0.14.5
- eyre: 0.4 => 0.6.8 - hashbrown: 0.9 => 0.14.5 - indexmap: 1.6 => 2.5.0 - num-complex: 0.2 => 0.4.6 - chrono-tz: 0.6 => 0.10 Eyre min-version is limited to 0.6.8 to be compatible with MSRV 1.63 Hashbrown min-version is limited to 0.14.5: rust-lang/hashbrown#574 Indexmap min-version is limited to 2.5.0 to be compatible with hashbrown 0.14.5
- eyre: 0.4 => 0.6.8 - hashbrown: 0.9 => 0.14.5 - indexmap: 1.6 => 2.5.0 - num-complex: 0.2 => 0.4.6 - chrono-tz: 0.6 => 0.10 Eyre min-version is limited to 0.6.8 to be compatible with MSRV 1.63 Hashbrown min-version is limited to 0.14.5: rust-lang/hashbrown#574 Indexmap min-version is limited to 2.5.0 to be compatible with hashbrown 0.14.5
Related to #571 / #572
On PyO3's MSRV CI runs (also 1.63, which
hashbrown
has in itsCargo.toml
) we are getting runtime panics from atomic orderings incompatible with 1.63.It looks like the root cause is the new
foldhash
dependency, which does not have anyrust-version
in itsCargo.toml
. The code in question has existed since the first release offoldhash
, so I can only conclude that crate does not support 1.63 at all, and thushashbrown
can't either.https://github.com/PyO3/pyo3/actions/runs/11271186265/job/31344727179#step:18:957
The text was updated successfully, but these errors were encountered: