[LocalCRE] Use OCR config from CapRegistry for evm capability

[bolekk]

No description provided.

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[github-actions]

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.

[github-actions]

CORA - Analysis Skipped

Reason: The number of code owners (2) is less than the minimum required (5) and/or the number of CODEOWNERS entries with changed files (1) is less than the minimum required (2).

[Tofel]

If we don't want to change this struct to handle local CRE's special case we could follow this route:

• add one more field to:

type PreEnvStartupOutput struct {
	DONCapabilityWithConfig []keystone_changeset.DONCapabilityWithConfig
    CapabilityToOCR3Config map[cre.CapabilityFlag]OCR3Config`
}

• and return the config we want to use for each capability that requires it
• then add CapabilityToOCR3Config map[cre.CapabilityFlag]OCR3Config to:

type ConfigureCapabilityRegistryInput struct {
	ChainSelector               uint64
	Topology                    *Topology
	CldEnv                      *cldf.Environment
	NodeSets                    []*NodeSet
	CapabilityRegistryConfigFns []CapabilityRegistryConfigFn
	Blockchains                 []blockchains.Blockchain

	CapabilitiesRegistryAddress *common.Address

	WithV2Registries bool

	DONCapabilityWithConfigs map[uint64][]keystone_changeset.DONCapabilityWithConfig
    CapabilityToOCR3Config map[cre.CapabilityFlag]OCR3Config
}

• and pass that to func ConfigureCapabilityRegistry(input cre.ConfigureCapabilityRegistryInput), which inside calls mustToV2ConfigureInput()
• finally modify `mustToV2ConfigureInput():

func (d *dons) mustToV2ConfigureInput(chainSelector uint64, contractAddress string, capabilityToOCR3Config map[cre.CapabilityFlag]OCR3Config) cap_reg_v2_seq.ConfigureCapabilitiesRegistryInput {

• and grab if from the map when executing embedOCR3Config()

[cl-sonarqube-production]

Quality Gate passed

Issues
3 New issues
2 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[trunk-io]

🔴 Test Results: Unrelated Failure

Affected failures:

1. Workflow Run: Integration Tests

What Broke

The TestToV2ConfigureInput in keystone_test.go is incorrectly passing a nil OCR3 configuration map when a capability is configured to use it, leading to a panic. Specifically, the test's donConfig includes a capability with UseCapRegOCRConfig: true, which causes dons.mustToV2ConfigureInput to attempt to look up an OCR3 config in the nil map, resulting in a panic.

Autofix Options

You can use our MCP server to get AI assistance with debugging and fixing these failures.

• Use MCP in your IDE to debug the issue. Try Help me fix CI failures from FbwI86Qm to get started.

Tip

Get Better Results: This CI job is not uploading test reports. Adding structured test reports enables more precise, test-level analysis with better root cause identification and more targeted fix recommendations.
👉🏻 Learn how to upload test results.