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

Update checkpoint file format version from v4 to v5 #2174

Conversation

fxamacker
Copy link
Member

@fxamacker fxamacker commented Mar 22, 2022

Changes include:

  • Bump version of checkpoint file to v5.
  • Support reading v4 for compatibility.
  • Add tests and test data to read v4.
  • Update root checkpoint extraction program to support all versions.

Updates #1944 (checkpoint file format v4)
Updates #2126 #2165 (checkpoint file format v5)

Bump version of checkpoint file to v5.
Support reading v4 for compatibility.
Add tests and test data to read v4.
if err != nil {
log.Fatal().Err(err).Msg("invalid root checkpoint")
}
} else {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if it would be a bit more future-proof if we have an upper version boundary here and error out if the version is higher than expected rather than assuming forward compatibility

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@m4ksio Great suggestion! 👍 Opened issue #2205 to track this and done in PR #2206.

@fxamacker fxamacker merged commit c90c1db into fxamacker/optimize-encoded-payload-value-length-in-checkpoint Mar 23, 2022
@fxamacker fxamacker deleted the fxamacker/bump-checkpoint-version branch March 23, 2022 17:18
@fxamacker fxamacker added the Execution Cadence Execution Team label Jul 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change Execution Cadence Execution Team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants