Repository navigation
test(compat): replay the next upgrade from mainnet events 1.8.0 - #170
Merged
Merged
Conversation
Mainnet now runs events 1.8.0 and profile 1.2.1, so the storage replay starts from those builds. The wasm fixtures are the live code fetched by hash, and mainnet-state.json is ledger 65,003,455, the first archive checkpoint after the upgrade. A second capture of that ledger produced the same file. The replay now upgrades events only, 1.8.0 to this tree's 2.1.0, because the profile here is still the deployed 1.2.1. It checks that the deployed build refuses an apply before its 17,280-ledger timelock, advances the ledger, then pauses, applies, migrates and unpauses as the runbook does. The test fails at the start if contracts/profile no longer reports 1.2.1, so a profile change cannot ship without being replayed. The pre-1.7.0 record checks are gone because mainnet converted those records.
Plan expiredYour subscription has expired. Please renew your subscription to continue using CI/CD integration and other features. |
…ay-from-1.8.0 # Conflicts: # BACKLOG.md # docs/storage-compatibility.md
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Mainnet runs events 1.8.0 and profile 1.2.1 since the 17 October upgrade. The storage replay still started from 1.7.0 and 1.2.0. This PR moves it to the new baseline, so the next mainnet upgrade (events 2.1.0) is checked against real mainnet state.
Fixtures:
mainnet-events-1.8.0.wasm(acf70ca0…) andmainnet-profile-1.2.1.wasm(8a8a1208…): the live code, fetched by hash withstellar contract fetch. They replace the 1.7.0 and 1.2.0 files.mainnet-state.json: contract data at ledger 65,003,455 (protocol 29, 2,295 entries), the first archive checkpoint after the upgrade. Running./scripts/capture-mainnet-compat-snapshot.shagain with no ledger argument reproduces it byte for byte.Replay changes (
contracts/compatibility/src/lib.rs):apply_upgradewithUpgradeTimelockNotElapsed.migrate_events, migrates and unpauses, following runbook Section 4.contracts/profileno longer reports 1.2.1, so a profile change has to add its own upgrade to the replay.Also updated:
docs/storage-compatibility.mddescribes the new baseline and the refresh steps, andBACKLOG.mdrecords the refresh as done.This PR and #169 both edit
BACKLOG.mdanddocs/storage-compatibility.md. Whichever merges second needs a small conflict fix.Checked locally:
cargo fmt --checkandcargo clippy --locked --all-targets -D warningspass.cargo test --workspace: 337 events and 60 profile tests pass../scripts/test-storage-compat.shpasses.