-
Notifications
You must be signed in to change notification settings - Fork 308
feat(contract_manager): improve manual reveal script #2767
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 8 Skipped Deployments
|
| "Usage: $0 --chain <chain-id> --private-key <private-key> --sequence-number <sequence-number>", | ||
| "Tries to reveal entropy requests with callback using the provided private key.\n" + | ||
| "This can be used to manually debug why a callback was not triggered or recover manually from a downtime\n" + | ||
| "Usage: $0 --chain <chain-id> --private-key <private-key> --sequence-number <sequence-number>", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be useful to add an example of a seq number range
| type: "string", | ||
| demandOption: true, | ||
| desc: "sequence number of the request to reveal", | ||
| desc: "Sequence number of the request to reveal or a range of sequence numbers to reveal separated by colon (e.g. 1000:1100)", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the second number inclusive or exclusive?
Summary
Make the manual reveal script to accept a range.
Rationale
Helpful for incident recovery
How has this been tested?