better logs for write report

[fernandezlautaro]

Improve troubleshooting WriteReport errors.
The retry.Do is swalloging internal error, making it hard to troubleshoot

Requires

• improve logs for retry.Do error scenarios(troubleshoting improvement) chainlink-common#1909

Supports

[github-actions]

I see you updated files related to core. Please run make gocs 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]

✅ No conflicts with other open PRs targeting develop

[Copilot]

Pull request overview

Risk Rating: MEDIUM

Improves observability for EVM SubmitTransaction failures (especially around receipt retrieval) and fixes a formatting issue in remote capability request logging to make troubleshooting “write report” paths easier.

Changes:

• Capture and log the last receipt-retrieval error from retry.Do in evmService.SubmitTransaction.
• Return a more detailed error on receipt-retrieval failure (including both “last” and “retry” errors).
• Fix a log call that previously used Warn with printf-style formatting by switching to Warnf.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
core/services/relay/evm/evm_service.go	Adds logging and richer error propagation for failed receipt retrieval during SubmitTransaction.
core/capabilities/remote/executable/request/client_request.go	Fixes incorrect logger method usage so formatted warning output is correct.

Areas needing scrupulous human review:

• core/services/relay/evm/evm_service.go:288-305 — retry/error composition and whether returned error strings are relied upon by callers/tests; confirm behavior under context timeout/cancel.
• core/services/relay/evm/evm_service.go:289-300 — confirm retry.Do semantics (e.g., whether the closure can be skipped on early context cancellation) match the new lastReceiptErr approach.

Reviewer recommendations (from CODEOWNERS):

• For core/capabilities/...: @smartcontractkit/keystone, @smartcontractkit/capabilities-team
• For overall/core ownership: @smartcontractkit/foundations, @smartcontractkit/core

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[pavel-raykov]

this seems like an ad-hoc solution. Could you please update https://github.com/smartcontractkit/chainlink-common/blob/main/pkg/utils/retry/retry.go with error wrapping so that the latest error is also returned as the retry.Do resut?

[fernandezlautaro]

nice catch, will do.

[github-actions]

CORA - Pending Reviewers

All codeowners have approved! ✅

Legend: ✅ Approved | ❌ Changes Requested | 💬 Commented | 🚫 Dismissed | ⏳ Pending | ❓ Unknown

For more details, see the full review summary.

[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