Skip to content

op-node/derive: CriticalError for missing beacon endpoint after Ecotone#19501

Merged
sebastianst merged 1 commit intodevelopfrom
seb/fix-19495-beacon-critical-error
Mar 12, 2026
Merged

op-node/derive: CriticalError for missing beacon endpoint after Ecotone#19501
sebastianst merged 1 commit intodevelopfrom
seb/fix-19495-beacon-critical-error

Conversation

@sebastianst
Copy link
Copy Markdown
Member

Summary

  • Fixes misconfiguration handling in DataSourceFactory.OpenData: wraps the "beacon endpoint not configured" error with NewCriticalError so the node stops with a clear fatal error instead of retrying indefinitely

Running a post-Ecotone node without --l1.beacon is an unrecoverable operator misconfiguration. The previous unclassified error caused infinite backoff+retry with misleading Error-level logs instead of a clean node halt.

Closes #19495. Part of #19491.

🤖 Generated by Claude Code

…red after Ecotone

Wraps the "beacon endpoint not configured" error with NewCriticalError
so the node stops with a clear fatal error instead of retrying
indefinitely on an unrecoverable operator misconfiguration.

Fixes #19495.
@sebastianst sebastianst requested review from a team and ajsutton March 12, 2026 16:18
Copy link
Copy Markdown
Contributor

@ajsutton ajsutton left a comment

Choose a reason for hiding this comment

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

LGTM. We should just make --l1.beacon a required flag now (if we haven't already).

@sebastianst
Copy link
Copy Markdown
Member Author

There's already a check for this in Config.Check() (config.go:137-144) — if EcotoneTime is set in the rollup config, the node will fail at startup with an error if no beacon endpoint is configured. The check in data_source.go is defense-in-depth for cases where the startup check is bypassed (e.g. in tests).

@sebastianst sebastianst added this pull request to the merge queue Mar 12, 2026
Merged via the queue into develop with commit b80de52 Mar 12, 2026
96 checks passed
@sebastianst sebastianst deleted the seb/fix-19495-beacon-critical-error branch March 12, 2026 21:56
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.

op-node/derive: missing beacon endpoint after Ecotone activation returns unclassified error instead of CriticalError

2 participants