core/services/workflows/v2: expand limited ChainRead method set

[jmank88]

https://smartcontract-it.atlassian.net/browse/PLEX-2111

Requires:

• pkg/settings/limits: fix double close chainlink-common#1812 (bumps default from 10 to 15)

[github-actions]

👋 jmank88, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[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.

[Tofel]

now that ChIP Ingress Test Sink PR has been merged I recommend using that instead of full ChIP stack.

If you do need to log all events, use GetLoggingPublishFn when starting the test sink instead of GetPublishFn. The former will save all events as JSON in a file.

If you do need to use the full stack for some reason you need to stop beholder in test clean up, because otherwise it will keep running on port 50051 and all tests that run after this one, which try to start the test sink will fail. Sink uses the same port as the real ChIP Ingress.

[jmank88]

Looks like this downgrade is causing problems

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 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: EVM Read Trigger Panic

Affected failures:

1. Workflow Run: Integration Tests

What Broke

The CI failure is caused by an issue within one of the newly introduced EVM read operations or the refactoring of the onReadTrigger function to handle multiple test cases. Specifically, the requireEvent function now fetches the latest block number using HeaderByNumber, which is a new point of failure.

Proposed Fixes

Modify the onReadTrigger function in system-tests/tests/smoke/cre/evm/evmread/main.go to explicitly log any recovered panic errors using the workflow's logger, ensuring better visibility of test failures in CI logs.

In main.go:54

 \tdefer func() {
 \t	if r := recover(); r != nil {
+ \t		runtime.Logger().Error("onReadTrigger panicked", "recovered", r, "testCase", cfg.TestCase.String(), "workflow", cfg.WorkflowName)
 \t		err = fmt.Errorf("panic: %v", r)
 \t	}
 \t}()

Autofix Options

You can apply the proposed fixes directly to your branch. Try the following:

• Comment /trunk stack-fix 9sZQ04CI to generate a stacked PR with the proposed fixes.
• Use MCP in your IDE to fix the issue. Try Help me fix CI failures from 9sZQ04CI 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.