Skip to content
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

Replace NodesFromJD with NodeInfo #15256

Merged
merged 10 commits into from
Nov 22, 2024
Merged

Replace NodesFromJD with NodeInfo #15256

merged 10 commits into from
Nov 22, 2024

Conversation

archseer
Copy link
Contributor

No description provided.

return nil, nil
}
// if nodeIDs starts with `p2p_` lookup by p2p_id instead
filterByPeerIDs := strings.HasPrefix("p2p_", nodeIDs[0])
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit implicit, but JD node IDs start with node_. p2p_ is a good indicator to filter by peer ID instead

Copy link
Contributor

github-actions bot commented Nov 15, 2024

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

@@ -278,6 +312,7 @@ func NodeInfo(nodeIDs []string, oc NodeChainConfigsLister) (Nodes, error) {
if err != nil {
return nil, err
}
// TODO: this is evm specific, make it work with aptos
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still need to address this

Copy link
Contributor

Flaky Test Detector for deployment/go.mod project has failed ❌

Ran new or updated tests between jd-improvements and dce776a (reuse-nodeinfo).

View Flaky Detector Details | Compare Changes

Failed Tests

Ran 19 tests in total for all affected test packages. Below are the tests identified as flaky, with a pass ratio lower than the 100% threshold:

TestPackage                                                TestName       PassRatio  RunCount   Skipped
---------                                                  ---------      ---------  ---------  ---------
github.com/smartcontractkit/chainlink/deployment/keystone  TestDeploy     0%         1          false
github.com/smartcontractkit/chainlink/deployment/keystone  TestDeployCLO  0%         1          false

Copy link
Contributor

Flaky Test Detector for deployment/go.mod project has failed ❌

Ran new or updated tests between jd-improvements and 311b042 (reuse-nodeinfo).

View Flaky Detector Details | Compare Changes

Failed Tests

Ran 19 tests in total for all affected test packages. Below are the tests identified as flaky, with a pass ratio lower than the 100% threshold:

TestPackage                                                                   TestName             PassRatio  RunCount   Skipped
---------                                                                     ---------            ---------  ---------  ---------
github.com/smartcontractkit/chainlink/deployment/keystone/changeset/internal  TestUpdateDon        0%         1          false
github.com/smartcontractkit/chainlink/deployment/keystone/changeset/internal  TestUpdateDon/empty  0%         1          false
github.com/smartcontractkit/chainlink/deployment/keystone                     TestDeploy           0%         1          false
github.com/smartcontractkit/chainlink/deployment/keystone                     TestDeployCLO        0%         1          false

Copy link
Contributor

Flaky Test Detector for deployment/go.mod project has failed ❌

Ran new or updated tests between jd-improvements and 759c3c1 (reuse-nodeinfo).

View Flaky Detector Details | Compare Changes

Failed Tests

Ran 19 tests in total for all affected test packages. Below are the tests identified as flaky, with a pass ratio lower than the 100% threshold:

TestPackage                                                                   TestName             PassRatio  RunCount   Skipped
---------                                                                     ---------            ---------  ---------  ---------
github.com/smartcontractkit/chainlink/deployment/keystone                     TestDeploy           0%         1          false
github.com/smartcontractkit/chainlink/deployment/keystone                     TestDeployCLO        0%         1          false
github.com/smartcontractkit/chainlink/deployment/keystone/changeset/internal  TestUpdateDon        0%         1          false
github.com/smartcontractkit/chainlink/deployment/keystone/changeset/internal  TestUpdateDon/empty  0%         1          false

@archseer archseer changed the base branch from jd-improvements to ks/jd-view November 21, 2024 04:44
Copy link
Contributor

Static analysis results are available

Hey @archseer, you can view Slither reports in the job summary here or download them as artifact here.
Please check them before merging and make sure you have addressed all issues.

Copy link
Contributor

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

🎖️ No JIRA issue number found in: PR title, commit message, or branch name. Please include the issue ID in one of these.

@archseer archseer marked this pull request as ready for review November 21, 2024 12:55
@archseer archseer requested review from a team, eutopian and yevshev as code owners November 21, 2024 12:55
@archseer archseer requested a review from krehermann November 21, 2024 12:55
Base automatically changed from ks/jd-view to develop November 21, 2024 15:45
@archseer archseer requested review from a team as code owners November 21, 2024 15:45
krehermann
krehermann previously approved these changes Nov 22, 2024
}

func (d RegisteredDon) signers() []common.Address {
func (d RegisteredDon) signers(chainFamily string) []common.Address {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would this be easier if passing the selector rather than the family? all the nodes have to have the registry chain enabled for the system to work so should be safe to pass the registry selector

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add a small test would give confidence of this func

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was actually the bug: I used the registry selector but the write nodes didn't have the registry chain defined, so the lookup was failing

// accountAddress string
// }

func toNodeKeys(o *deployment.Node, registryChainSel uint64) NodeKeys {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add a small test?

deployment/keystone/types.go Outdated Show resolved Hide resolved
@archseer archseer force-pushed the reuse-nodeinfo branch 2 times, most recently from 52f12d2 to c588ee2 Compare November 22, 2024 06:29
krehermann
krehermann previously approved these changes Nov 22, 2024
@krehermann krehermann requested a review from jmank88 November 22, 2024 13:52
connorwstein
connorwstein previously approved these changes Nov 22, 2024
@krehermann krehermann dismissed stale reviews from connorwstein and themself via fc2afb9 November 22, 2024 16:39
@archseer archseer added this pull request to the merge queue Nov 22, 2024
Merged via the queue into develop with commit a267825 Nov 22, 2024
150 checks passed
@archseer archseer deleted the reuse-nodeinfo branch November 22, 2024 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants