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

[Compat] Fixes for a variety of backward compatibility issues #1920

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

AhmedSoliman
Copy link
Contributor

@AhmedSoliman AhmedSoliman commented Sep 3, 2024

[Compat] Fixes for a variety of backward compatibility issues

Addresses the known backward incompatibility issues with v1.0 including the issue introduced in #1692


Stack created with Sapling. Best reviewed with ReviewStack.

Addresses the known backward incompatibility issues with v1.0 including the issue introduced in #1692
@AhmedSoliman AhmedSoliman changed the title [Compat] Avoid the old seal logstate field [Compat] Fixes for a variety of backward compatibility issues Sep 3, 2024
Copy link

github-actions bot commented Sep 3, 2024

Test Results

15 files  ±0  15 suites  ±0   19m 59s ⏱️ +2s
 6 tests ±0   6 ✅ ±0  0 💤 ±0  0 ❌ ±0 
18 runs  ±0  18 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 4ae1875. ± Comparison against base commit aff506c.

♻️ This comment has been updated with latest results.

Copy link
Contributor

@pcholakov pcholakov left a comment

Choose a reason for hiding this comment

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

Just waiting for e2e tests, and will report back.

Comment on lines +144 to +147
#[serde(default)]
seal: Option<SealReason>,
#[serde(default)]
pub sealed: bool,
Copy link
Contributor

Choose a reason for hiding this comment

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

Simple as that! Thank you for fixing this.

@AhmedSoliman AhmedSoliman merged commit 4ae1875 into main Sep 3, 2024
12 checks passed
@AhmedSoliman AhmedSoliman deleted the pr1920 branch September 3, 2024 17:12
@pcholakov
Copy link
Contributor

Success! I can now go back and forth between 1.0.2 and the 1.1.0-main binaries on the same store with no errors, and the state table dump is identical. Not a very thorough test yet but it's a start.

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.

2 participants