Repository navigation
Conversation
A single node with an unparsable JD chain ID made NodeInfo return a non-ErrMissingNodeMetadata error, so GenerateNopsView and GenerateNOPsViewV2 discarded every node. Continue with the partial node list instead and log a warning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
✅ No conflicts with other open PRs targeting |
This branch has not been deployed
This file contains hidden or 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
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.
One staging node exported its JD chain ID as
"11155111 ethereum-testnet-sepolia".NodeInforeturned a non-ErrMissingNodeMetadataerror for it, soGenerateNopsViewandGenerateNOPsViewV2discarded all ~70 nodes, and the CLD nightly job committed a stagingstate.jsonwithoutnops/nops_v2(CLD commit 496134e).The views now continue with the node list
NodeInforeturns and log a warning, so only the bad node loses its chain-derived fields. They still fail whenNodeInforeturns no nodes.NodeInfoitself is unchanged, so changesets that need complete node metadata still fail hard.Related CLD safety net: smartcontractkit/chainlink-deployments#21784.
Deployment Validation: Next CLD nightly state runs keep
nops/nops_v2populated when a node has malformed JD chain config.🤖 Generated with Claude Code