-
Notifications
You must be signed in to change notification settings - Fork 97
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
feat: retry query signature verification in case cache is stale #801
Conversation
size-limit report 📦
|
It's throwing an error, but not in a way that the mitm test is detecting as a "rejection" I need to investigate a bit further |
'Invalid signature from replica signed query: no matching node key found.', | ||
); | ||
} | ||
return this.#verifyQueryResponse(query, updatedSubnetStatus); |
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 it okay that there is no resolve(subnetStatus);
call here, in between get
and verifyQueryResponse
, as in the above code?
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.
Yes, we are not within a Promise
at this stage in the code (apart from the async query
function itself). It's a little semantically incongruous if you're comparing this section to the above sections, however
Description
Because a node can be upgraded while the cache is stale, we should retry a failed query signature verification once, after refreshing the cache
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
Checklist: