This repository has been archived by the owner on Jun 3, 2020. It is now read-only.
Validate chains are registered on startup #376
Merged
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.
Previously chains were checked lazily at the time their pubkeys were fetched or signing was requested.
This adds an eager check at the time clients start.
It would probably be better if this check mapped to some sort of known-good handle (e.g.
Index
into a generational arena), but this is enough to catch the error eagerly instead of lazily.I encountered this personally during the
cosmoshub-3
upgrade.