Skip to content

fix(timelock): suppress event-id burst notices - #462

Merged
spalen0 merged 1 commit into
mainfrom
fix/drop-timelock-burst-notices
Nov 5, 2026
Merged

spalen0 merged 1 commit into
mainfrom
fix/drop-timelock-burst-notices

Conversation

@spalen0

@spalen0 spalen0 commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

Timelock batches with more than 10 new events currently post an internal notice containing only chain and event IDs, such as the 21 Maple proposals scheduled in one transaction. Suppress those burst notices while continuing to record every event in the inbox and report. Smaller event notices and diagnostics for websocket misses, outages, reconciliation failures, and reorgs continue to work. Morpho burst notices keep their current behavior.

Validation: 94 subscriber tests passed, including burst handling over WS and HTTP, event retention, and websocket-miss reporting. Ruff lint/format and type checks passed for the changed Python files.

After merge and production code sync, restart monitoring-timelock-subscriber to load the change.

@spalen0
spalen0 marked this pull request as ready for review November 5, 2026 21:30
@spalen0
spalen0 merged commit 082f4e9 into main Nov 5, 2026
3 checks passed
@spalen0
spalen0 deleted the fix/drop-timelock-burst-notices branch November 5, 2026 21:30
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.

1 participant