Skip to content

fix(continuous): warn-only payload-channel sends#535

Open
julio4 wants to merge 1 commit into
mainfrom
fix/continuous-publish-error-handling
Open

fix(continuous): warn-only payload-channel sends#535
julio4 wants to merge 1 commit into
mainfrom
fix/continuous-publish-error-handling

Conversation

@julio4

@julio4 julio4 commented Jun 12, 2026

Copy link
Copy Markdown
Member

Reuse notify_built_payload in continuous publish_candidate + warn built_fb_payload_tx instead of propagating error

…tinuous mode

In continuous mode, `publish_candidate` was treating a full
`built_fb_payload_tx` channel as a fatal error via `?`, which killed the
entire payload job whenever the payload handler stalled (e.g. on a slow
p2p peer). The per-trigger path in `notify_built_payload` has always
treated the same condition as warn-and-continue. This fix replaces the
fatal `try_send` / partial-warn pattern with a call to the existing
`notify_built_payload` (widened to `pub(crate)`) and corrects the
publish ordering to match the old path: ws publish → send_replace →
notify_built_payload → timing metric. The now-dead `built_fb_payload_tx`
and `built_payload_tx` accessor methods are removed; all callers are
consolidated into `notify_built_payload`.
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.

2 participants