Skip to content
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

fix: pin ahash to 0.8.0 #3048

Closed
wants to merge 1 commit into from
Closed

Conversation

mattbonnell
Copy link

0.8.1 has a bug tkaitchuck/aHash#143

@github-actions github-actions bot added the arrow Changes to the arrow crate label Nov 8, 2022
@tustvold
Copy link
Contributor

tustvold commented Nov 8, 2022

I believe this pin be just added by impacted downstreams, i.e. those that are using custom build tooling. I'm not sure we need to pin this here?

@mattbonnell
Copy link
Author

I believe this pin be just added by impacted downstreams, i.e. those that are using custom build tooling. I'm not sure we need to pin this here?

Can you pin a sub-dependency?

@tustvold
Copy link
Contributor

tustvold commented Nov 9, 2022

Yes

@mattbonnell
Copy link
Author

mattbonnell commented Nov 9, 2022

Yes

I had tried but it didn’t seem to be working. Will try again.

Even so, ahash-8.0.1 uses cfg-target-abi, which is unstable. Doesn’t this then mean that installing arrow will fail for anyone not running a nightly, as it is for me?

@tustvold
Copy link
Contributor

tustvold commented Nov 9, 2022

My understanding is it is just ignored outside of nightly

@mattbonnell
Copy link
Author

mattbonnell commented Nov 9, 2022

My understanding is it is just ignored outside of nightly

You mentioned this would affect folks using custom build tooling. I’m using Bazel, are tou saying that might be related?

@tustvold
Copy link
Contributor

tustvold commented Nov 9, 2022

Yes, we had issues with hakari parsing the ahash crate, that @carols10cents tracked down to EmbarkStudios/cfg-expr#52 (comment)

My understanding is that some parsers don't correctly understand unstable cargo build attributes, and this causes custom build tooling to fail.

@@ -38,10 +38,10 @@ path = "src/lib.rs"
bench = false

[target.'cfg(target_arch = "wasm32")'.dependencies]
ahash = { version = "0.8", default-features = false, features = ["compile-time-rng"] }
ahash = { version = "0.8.0", default-features = false, features = ["compile-time-rng"] }
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
ahash = { version = "0.8.0", default-features = false, features = ["compile-time-rng"] }
ahash = { version = "=0.8.0", default-features = false, features = ["compile-time-rng"] }

FYI you will need an exact version pin, cargo applies semver compatibility by default

@tustvold
Copy link
Contributor

Closing this, as workarounds exist, and the change to ahash has been reverted - tkaitchuck/aHash#145

@tustvold tustvold closed this Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arrow Changes to the arrow crate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants