-
Notifications
You must be signed in to change notification settings - Fork 219
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!: upgrade bitflags crate #5831
Merged
SWvheerden
merged 9 commits into
tari-project:development
from
brianp:chore-upgrade-bitflags
Oct 11, 2023
Merged
chore!: upgrade bitflags crate #5831
SWvheerden
merged 9 commits into
tari-project:development
from
brianp:chore-upgrade-bitflags
Oct 11, 2023
Conversation
This file contains 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
bitflags uses an internal structure that can't be serialized by borsh. This format of creating the struct and using the bitflags trait is the recommended format for supporting not supported serializers.
Upgrade to the new format. This reverts commit 1a44de6. With a bit extra ammended into it...
ghpbot-tari-project
added
P-acks_required
Process - Requires more ACKs or utACKs
P-reviews_required
Process - Requires a review from a lead maintainer to be merged
labels
Oct 4, 2023
SWvheerden
changed the title
chore: upgrade bitflags crate
chore!: upgrade bitflags crate
Oct 5, 2023
SWvheerden
reviewed
Oct 6, 2023
Co-authored-by: SW van Heerden <[email protected]>
hansieodendaal
approved these changes
Oct 9, 2023
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.
utACK
ghpbot-tari-project
removed
the
P-reviews_required
Process - Requires a review from a lead maintainer to be merged
label
Oct 9, 2023
SWvheerden
approved these changes
Oct 11, 2023
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.
Description
Upgrade the bitflags crate to 2.4.0. This made a few notable changes:
{"bits": 0}
to just outputting the compact bit0
. It is possible to maintain the legacy format but we don't need to keep that.Motivation and Context
We wanted to upgrade before release.
Closes: #5669
See v2 release changes for bitflags
How Has This Been Tested?
CI
What process can a PR reviewer use to test or verify this change?
Review the changes
Breaking Changes
BREAKING CHANGE: May not be able to communicate with older nodes. Will require users to upgrade their nodes