Fix misnomer and warn when StakedNodes fails to update. #130
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SOELTH
force-pushed
the
h/staked-nodes-sanity
branch
from
14a531a
to
b00ca4b
Compare
SOELTH
force-pushed
the
h/staked-nodes-sanity
branch
from
b00ca4b
to
27aabd6
Compare
segfaultdoc
reviewed
May 6, 2024
jedleggett
approved these changes
May 8, 2024
buffalu
approved these changes
May 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many operators have been reporting that TPU-Forwards returns DISALLOWED even when connecting with high-staked identity keys. One possible reason for this is that StakedNodes is not updating properly.
Operators should be aware of this because this essentially bricks their TPU staked connections.