Repository navigation
fix(lib): session bridge reports a failed server start and stops the right watcher #9796
Description
Parent: #7303 (DX-9, DX-11; the sync-shared-copies allowlist gate is removed).
Problem
- DX-9: server output goes to
/dev/null, so a failed start reports no cause. - DX-11:
stoppicks the watcher by the data dir's last path component, which isinterview-surfacein every topic, so it can stop another topic's watcher.
The canonical copy is lib/session-bridge/ (session_bridge.py, watch.sh, wake.sh); scripts/shared-copies.txt lists the copies to sync.
Done when
- A failed server start prints the server's stderr tail and exits non-zero; a test covers it and passes.
-
stopmatches the watcher by the full data-dir path; a test with two topics proves it stops only the named one. - Every copy listed in
scripts/shared-copies.txtfor these files matches the canonical copy (the repo's shared-copy check passes). -
scripts/check-changelog-fragments.shpasses.
Activity
github-actions commentedon Oct 24, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Medium
Complexity: Medium
Uncertainty: Known
Flags: none
Understood: two defects in the session bridge. (1) A failed server start hides its cause because output goes to /dev/null. It should print the stderr tail and exit non-zero. (2)
stopmatches watchers by the last path component of the data dir, so it can stop another topic's watcher. It should match the full path. Both changes need tests, the shared copies must be synced, and the changelog fragment check must pass. The scope and done-when items are clear. I found no likely duplicates.Automated triage, applied by the lanes App.