-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add random chance to panic mode for DependencyAudit #35
Add random chance to panic mode for DependencyAudit #35
Conversation
panic("This transaction is using dependencies not staged for Crescendo upgrade coming soon! Learn more: https://bit.ly/FLOWCRESCENDO. Dependencies not staged: ".concat(unstagedDependenciesString)) | ||
} else { | ||
emit UnstagedDependencies(dependencies: unstagedDependencies) | ||
self.maybePanicOnUnstagedDependencies(unstagedDependencies) |
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.
I think I'm missing something - why do we want to randomly panic here? I would think we'd want clear expectations around whether unstaged dependencies panic or not.
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.
The business requirement is that there would be a random chance the transaction would fail if it is missing dependencies. That random chance would start at 0% and increase to 100% just before the spork.
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.
I see. I still don't understand the rationale behind that product decision, but not sure this is the place to discuss prod reqs so I'll just review based on that stated requirement
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.
A couple comments about events and input validation. The premise of linearly increasing probability of reversion on unstaged dependencies seems to be implemented correctly
Description
Add the ability to set an end and start block between which the change of a transaction with unstaged dependencies panicking linearly increases.
For contributor use:
main
branchFiles changed
in the Github PR explorer