-
Notifications
You must be signed in to change notification settings - Fork 135
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
chore: pin crunchy for Windows compatibility #1670
Conversation
Still working on testing it locally |
Shouldn't you push the updated lock file as well? |
Yeah, I will before taking it out of Draft. But I'm finding that it locally is still allowing crunchy to go to 0.2.3 |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR overall looks good, of course pushing the updated lock files which uses the patch is required for CI to pass
Cargo.toml
Outdated
# get the wrong path, update this when the workflow has been updated | ||
# | ||
# See: https://github.com/eira-fransham/crunchy/issues/13 | ||
crunchy = { git = "https://github.com/eira-fransham/crunchy", ref = "1bf90cf2d0a8cfcb2c5592275a23ab028dff6468" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
crunchy = { git = "https://github.com/eira-fransham/crunchy", ref = "1bf90cf2d0a8cfcb2c5592275a23ab028dff6468" } | |
crunchy = { git = "https://github.com/eira-fransham/crunchy", rev = "1bf90cf2d0a8cfcb2c5592275a23ab028dff6468" } |
this must be rev instead of ref
Weird that the tooling didn't complain about ref. It's maybe the only time that Rust tooling has been too relaxed for my taste. X) |
Need the patch for all the sub-dependencies
What was wrong?
Windows build is failing: https://github.com/ethereum/trin/actions/runs/13189513029/job/36819458339
How was it fixed?
Pin crunchy for all dependencies