Kanban dispatcher singleton and concurrency fixes
Cluster 41448 · gateway. Data as of
Nothing open on GitHub. Fix merged in #49068 on 19 Jun 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #49068. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address a concurrency problem where multiple gateway instances can run competing kanban dispatchers simultaneously, leading to claim-reclaim churn and potential database corruption. Proposed fixes involve machine-global singleton locks and flock-based guards to enforce a single active dispatcher.
Open issues0
Open PRs0
Fixes on record
-
#49068 fix(kanban): machine-global singleton lock for the embedded dispatcher (#41448)
files:
gateway/kanban_watchers.py,scripts/release.py,tests/gateway/test_kanban_watchers_mixin.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#41448[Bug]: kanban dispatcher: gateway embeds dispatcher without singleton guard — two gateway instances cause claim-reclaim churn
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #49068
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 19 Jun 2026