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

Changes needed to support the modified speculative execution in the sidecar #16

Conversation

rafal-ch
Copy link

No description provided.

@rafal-ch rafal-ch marked this pull request as draft March 26, 2024 12:47
@rafal-ch rafal-ch changed the base branch from feat-2.0-spicy-wip-merge to feat-2.0-integration-pr March 29, 2024 08:03
@EdHastingsCasperAssociation
Copy link
Owner

will this be ready for review soon?

4636: Return None in case of an error in get_addressable_entity r=jacek-casper a=jacek-casper

The current behaviour causes a problem in NCTL upgrade scenario 11, where we use `get_total_supply_key` from the state upgrade script. The `get_addressable_entity` function fails instead of returning None, while `get_total_supply_key` expects it to return None in order to handle the legacy format. The error type here has already been converted to a String, so we can't match precisely on the NotFound error.

Co-authored-by: Jacek Malec <[email protected]>
@rafal-ch
Copy link
Author

rafal-ch commented Apr 3, 2024

will this be ready for review soon?

The plan is to keep this PR (and the other three for sidecar, client and casper-test) in draft until the feat-2.0-integration-pr branch is merged to feat-2.0.

Until then I keep these branches up-to-date with the changes landing in feat-2.0-integration-pr branch.

Rafał Chabowski and others added 4 commits April 3, 2024 10:35
@rafal-ch
Copy link
Author

rafal-ch commented Apr 4, 2024

Closed in favor of casper-network#4643

@rafal-ch rafal-ch closed this Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants