You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 94d9554
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(webapp,run-engine): route the realtime runs feed through one per-env change channel
Rework the new realtime runs backend (still behind its feature flag, with the
existing backend as the default) so every feed is a predicate over one
self-describing change record, published once per run change to a single
per-environment channel.
A per-instance router indexes the currently-held feeds by run, tag, and batch.
On a change it hydrates the affected runs once and serializes them once, then
fans the result to every matching feed, so one hot shared tag costs a single
query and serialize no matter how many feeds watch it. Newly triggered runs
surface immediately (the run-created event now carries tags and batch) rather
than waiting for a status change. An admission gate bounds how many cold
ClickHouse resolves run concurrently, so a mass reconnect across distinct
filters queues instead of stampeding the database. Live long-polls hold for
about 20 seconds to match the existing backend cadence.
0 commit comments