WhatsApp bridge pidfile process ownership fixes
Cluster 116883. Data as of
Nothing open on GitHub. Fix merged in #117556 on 20 Sep 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 #117556. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117556. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address bugs where the WhatsApp bridge's legacy pidfile mechanism could incorrectly identify or kill unrelated processes, including a fallback to matching 'node' as a cmdline substring. Fixes add stricter fingerprinting and ownership checks before acting on pidfiles.
Open issues0
Open PRs0
Fixes on record
-
#117556 fix(whatsapp): a legacy bridge pidfile no longer kills a stranger that mentions the session path (#116883, salvage #117139)
files:
plugins/platforms/whatsapp/adapter.py,tests/gateway/test_whatsapp_bridge_pidfile.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#117139 fix(whatsapp): refuse legacy-pidfile kills without a start-time fingerprint · merged via another change →
7a23b00,#117556
Closed issues · 1
- Closed#116883[Bug]: WhatsApp bridge ownership falls back to "node" in cmdline substring
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
- Merged PRs
- #117556
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026