-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Fix add and remove don #16523
Fix add and remove don #16523
Conversation
AER Report: CI Core ran successfully ✅AER Report: Operator UI CI ran successfully ✅ |
|
Flakeguard SummaryRan new or updated tests between View Flaky Detector Details | Compare Changes Found Flaky Tests ❌1 Results
ArtifactsFor detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json. |
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 issue here that "nonce" has been taken and can't be used again? even if the DON corresponding to that nonce has been removed?
Not sure it can be directly related to nonce , here is the removeDon ref which deletes the entry , next time when you next time try to add another DON it just increments the counter - it does not check whether the previous id is available because of the deletion |
* remove don fix * fixes * fix lint
While calculating next DONID addDon cs was calling
LatestCCIPDon
.If you remove the last don (n) LatestCCIPDon only gets
n-1
, and then sends expectedDonID asn
but the expectedDonID in Capreg is not reclaimed asn
for newly added don, it gets added with n+1 , therefore the addDon reverts with DonIdMismatch reason.Replacing the
LatestCCIPDon
call withgetNextDonId
call from capreg to ensure it returns next available don id for adding a don.