audio capture read_available stall fixes and fallbacks
Cluster 118552. Data as of
Nothing open on GitHub. Fix merged in #127197 on 30 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 #127197. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #127197. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where polling read_available stalls indefinitely on certain audio backends (notably DirectSound on Windows), causing wake-word detection and voice capture to hang. Fixes introduce fallback to blocking reads when the poll makes no progress.
Open issues0
Open PRs0
Fixes on record
-
#127197 fix(wake): recover transient capture read failures and fall back to blocking reads when read_available stalls
files:
tests/tools/test_wake_word.py,tests/tools/test_wake_word_stream_recovery.py,tools/wake_word.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#118560 fix(voice): fall back to blocking reads when read_available never advances · done elsewhere →
d79de94,#127197
Closed issues · 1
- Closed#118552[Bug]: Wake-word never fires on Windows — `_Capture.read()`'s `read_available` poll spins forever on DirectSound devices (regression from #117096 fix)
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
- #127197
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 30 Sep 2026