Kanban connect() flock hang fix iterations
Cluster 36644 · gateway. Data as of
Nothing open on GitHub. Fix merged in #50353 on 21 Jun 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #50353. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #50353. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was identified where kanban_db.connect() could hang indefinitely due to an unbounded fcntl.flock(LOCK_EX) call under concurrent access. Several follow-up fixes iterated on bounding, salvaging, and ultimately skipping the cross-process init lock to address the hang.
Open issues0
Open PRs0
Fixes on record
-
#50353 fix(kanban): bound the cross-process init lock so connect() can't hang forever
files:
hermes_cli/kanban_db.py,tests/hermes_cli/test_kanban_db.py,tests/hermes_cli/test_kanban_init_lock_bounded.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#37216 fix(kanban): skip cross-process flock on steady-state connect() (#36644) · done elsewhere →
84ba83b,#36644
Closed issues · 1
- Closed#36644[Bug]: Kanban dispatcher hangs forever on an unbounded fcntl.flock(LOCK_EX) in kanban_db.connect() under concurrent board access
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.67: 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
- #50353
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 21 Jun 2026