-
Notifications
You must be signed in to change notification settings - Fork 796
notary: Add admin rescue commands #4474
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
base: main
Are you sure you want to change the base?
Conversation
…bridge validation - Replace TxID-based deduplication with MessageID for pending message queue - Add emitter address validation for token bridge transfers - Fix test helper functions to generate unique messages with proper sequence numbers - Add duplicate prevention tests and improve error handling
…token bridges are not given a bad ruling
- Add commands to change the status of delayed and blackholed messages in the Notary - Change Notary commands to use MessageID consistently instead of a combination of pointers to MessagePublication and VAAHash
a18ad48
to
4fb9de5
Compare
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.
Just reviewed the latest commit
} | ||
|
||
return &nodev1.NotaryBlackholeDelayedMessageResponse{ | ||
Response: "Blackholed message", |
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.
Can you add in the vaaId
string into the responses?
} | ||
|
||
// RemoveBlackholedMsg removes a message from the blackholed list and deletes it from the database. | ||
func (n *Notary) RemoveBlackholedMsg(msgID string) error { |
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.
Should we add such messages that are removed from the blackholed list to the pending queue with 0 release time to ensure they are processed? I'm going to guess a reobservation would most likely lead to the message being blackholed again
string response = 1; | ||
} | ||
|
||
message NotaryResetReleaseTimerRequest { |
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.
Missing the admin command for this message
|
||
// When a message is blackholed, it should be removed from the delayed list and database. | ||
err := n.removeDelayed(msg) | ||
err := n.removeDelayed(msg.MessageID()) |
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.
Probably applies to the notary PR rather than this one, but should we attempt to remove from the delayed list + database before adding to the blackholed list? Just in case the removal fails we don't want the message in both places
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 have reviewed this PR and have no comments. 👍
Now that the Notary has been merged, this is in my court to rebase and fix-up. In doing so I'll go back and respond to the comments |
in the Notary
combination of pointers to MessagePublication and VAAHash
This PR is based on #4315 and will stay in draft until that PR is merged.