WhatsApp bridge lifecycle logs missing timestamps
Cluster 97021. Data as of
Nothing open on GitHub. Fix merged in #126259 on 28 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 #126259. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #126259. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address WhatsApp bridge lifecycle console lines (startup, connected, logged-out, reconnect) appearing in bridge.log without timestamps. The work involves adding timestamp formatting to the relevant console.log/warn calls in bridge.js.
Open issues0
Open PRs0
Fixes on record
-
#126259 fix(whatsapp): every bridge.log console line carries a timestamp (#97021, salvages #97105)
files:
scripts/whatsapp-bridge/bridge.js,scripts/whatsapp-bridge/bridge_helpers.js,scripts/whatsapp-bridge/bridge_helpers.timestamp.test.mjs
1 PR closed without merging
From the close comments: done elsewhere 1
-
#97105 fix(whatsapp): timestamp bridge.js's lifecycle console.log/warn lines · done elsewhere →
1e2498a,#126259
Closed issues · 1
- Closed#97021[Bug]: WhatsApp bridge lifecycle console lines (startup/connected/logged-out/reconnect) reach bridge.log with no timestamps
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
- #126259
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 28 Sep 2026