-
Notifications
You must be signed in to change notification settings - Fork 79
[LUM-753] Add diagnostic logging to dictation recording lifecycle #24067
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
tkheyfets
merged 1 commit into
main
from
devin/1775588602-LUM-753-dictation-diagnostic-logging
Apr 8, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚩 Pre-existing: awaitingDaemonResponse reset in stopRecording() after overlay check
At line 971,
awaitingDaemonResponseis reset tofalseimmediately after the overlay-dismiss check at line 968. In the dictation flow,handleFinalTranscriptionsetsawaitingDaemonResponse = true(line 878), then the recognition callback callsstopRecording()which checks the flag (preserving the overlay) but then resets it. WhenhandleDictationResponselater arrives (line 893-894), the flag is alreadyfalse. This means any code that checksawaitingDaemonResponsebetweenstopRecording()andhandleDictationResponsewill seefalse. This is pre-existing behavior unaffected by this PR, and the only consumer of the flag during that window appears to be anotherstopRecording()call (which would dismiss the overlay prematurely if triggered). Worth noting but not a regression.Was this helpful? React with 👍 or 👎 to provide feedback.