Pin to weezl 0.1.8 to resolve CI test failures#206
Closed
bushrat011899 wants to merge 1 commit into
Closed
Conversation
Issue appears to be caused upstream
This was referenced May 15, 2025
Contributor
Author
|
Opened an issue here just in case this is an upstream issue. I could see the release notes highlighted a change in behvaiour, but I'm not certain if this failure is intentional, and if so, what the remedy is. |
Contributor
|
It's important to find out whether that's breakage in weezl or a bug in this crate. Either way there's a bug somewhere, and pinning the version won't fix it, only crate compatibility problems with the crates ecosystem. |
Contributor
Author
|
Absolutely, unfortunately I'm not familiar enough with |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Objective
CI currently fails for a reason seemingly unrelated to the PR itself. I have diagnosed the issue as likely being caused by
weezl0.1.9. I verified this by usingcargo update --preciseto toggle between 0.1.8 and 0.1.9 and could observe the test failures on 0.1.9, and passed on 0.1.8.Solution