mtc_worker: Fix shard1, create shard2 #141
Merged
Conversation
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
A previous commit (a6868ea) changed the log ID and cosigner ID for dev1, dev2, and shard1. This was a breaking change, since older checkpoints can no longer be opened. In order to allow safe deployment to shard1, revert its log ID to the old one and add a cosigner ID with the same relative OID. Meanwhile, create a new log, shard2, with the cosigner and log ID we picked.
bwesterb
reviewed
Oct 27, 2025
| "log_id": "44363.48.5", | ||
| "cosigner_id": "44363.48.6", | ||
| "log_id": "13335.1", | ||
| "cosigner_id": "13335.1", |
bwesterb
approved these changes
Oct 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
A previous commit (a6868ea) changed the log ID and cosigner ID for dev1, dev2, and shard1. This was a breaking change, since older checkpoints can no longer be opened.
In order to allow safe deployment to shard1, revert its log ID to the old one and add a cosigner ID with the same relative OID.
Meanwhile, create a new log, shard2, with the cosigner and log ID we picked.