Timmy e6865a1bc6 fix: stop event-triggers Lagged handler from re-emitting via the same channel ...

Merge 1061 added a replay_current_pipeline_state() call to the broadcast::Lagged
branch, but replay broadcasts one event per CRDT item (~997) into a 256-slot
channel, deterministically re-overflowing it and triggering another Lagged. The
loop pinned CPU and likely caused today's machine crash. Revert to the pre-1061
behaviour of logging and continuing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-14 22:33:14 +01:00

..

migrations

huskies: merge 1061

2026-05-14 20:12:51 +00:00

src

fix: stop event-triggers Lagged handler from re-emitting via the same channel

2026-05-14 22:33:14 +01:00

build.rs

Restore codebase deleted by bad auto-commit e4227cf

2026-03-22 19:07:07 +00:00

Cargo.lock

huskies: merge 548_refactor_rename_living_spec_standalone_to_huskies_in_package_json_and_cargo_lock

2026-04-12 14:50:38 +00:00

Cargo.toml

docs: explain why libsqlite3-sys is pinned to 0.35 in server/Cargo.toml

2026-05-14 19:27:39 +01:00