Skip to content

Fix error classification for execution handler not found - #23567

Merged
vreff merged 1 commit into
developfrom
relay-fix-error-classification
Aug 28, 2026
Merged

Fix error classification for execution handler not found#23567
vreff merged 1 commit into
developfrom
relay-fix-error-classification

Conversation

@vreff

@vreff vreff commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes error classification in the confidential relay handler when an execution handler is not found, so it's treated as a user error instead of a system error.

Changes

  • core/capabilities/confidentialrelay/handler.go: reclassify the "execution handler not found" case.
  • handler_test.go: update the expectation to match.

Why

A missing execution handler is a workflow-author error (the workflow referenced a handler that doesn't exist), not an infrastructure failure — it shouldn't trigger system-error paging.

@vreff
vreff requested a review from a team as a code owner August 27, 2026 18:14
@github-actions

Copy link
Copy Markdown
Contributor

👋 vreff, 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!

@0xjeremyfrank 0xjeremyfrank left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM

@github-actions

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

@github-actions

Copy link
Copy Markdown
Contributor

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.

@trunk-io

trunk-io Bot commented Aug 27, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic Badge

Failed Test Failure Summary Logs
Test_CRE_V2_Solana_LogTrigger/Solana_LogTrigger The test failed due to an error in compiling the Go workflow caused by a network stream error while downloading a dependency. Logs ↗︎
Test_CRE_V2_Solana_LogTrigger The test failed without a specific error message, indicating an unspecified failure during execution. Logs ↗︎

View Full Report ↗︎Docs

@cl-sonarqube-production

Copy link
Copy Markdown

@vreff
vreff added this pull request to the merge queue Aug 28, 2026
Merged via the queue into develop with commit 282c35d Aug 28, 2026
377 of 384 checks passed
@vreff
vreff deleted the relay-fix-error-classification branch August 28, 2026 12:19
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.

3 participants