-
Notifications
You must be signed in to change notification settings - Fork 212
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
Various swing-store fixes #7259
Conversation
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.
Ya know, some days ya just gotta clean the bathroom, but it still makes everybody smile.
@warner this touches some types you were having trouble with, I just want to make sure this won't break any changes you may have in flight. |
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.
Looks good, thanks for the heads up. I don't think the new types will affect my other PR.
@Mergifyio unqueue |
☑️ The pull request is not queued |
bb070ce
to
231b8c5
Compare
231b8c5
to
b1343b7
Compare
refs: #7026
Description
This is a grab bag of swing-store changes and fixes. Some are required for the state-sync PR and extracted from it (#7225), some are follow up from #7026.
Most commits are independent, and best reviewed separately.
Security Considerations
This adds a few more consistency checks on the swing-store tables, ensuring that the data doesn't get in an unexpected state due to bugs or bad manipulations of the raw DB.
Scaling Considerations
None
Documentation Considerations
Some type changes are there to be more explicit about the expected usage and values.
Testing Considerations
Manually testing against state-sync branch