Closed
Write transcript to file every 20 s and refresh note summary after each write#6
Conversation
…each write - LIVE_CHUNK_MS changed from 5000 → 20000 ms so transcription chunks are written to the transcript file every 20 seconds (data-loss prevention: the note is kept current throughout the recording; a crash or unexpected close loses at most ~20 s of content) - After each successful transcriptAppend during a live chunk, call refreshSummaryFromFile() so the note's summary block is updated from the freshly-written file. Both operations share a try/catch so errors are caught and logged cleanly. - The forced final flush at Stop (force=true) skips the in-chunk summary refresh because handleRecordingStop already calls refreshSummaryFromFile() explicitly after the tail is appended. - Updated comments throughout to accurately describe the new behaviour. - All 105 existing tests continue to pass.
Copilot
AI
changed the title
[WIP] Update transcription to write every 20 seconds
Write transcript to file every 20 s and refresh note summary after each write
Jul 2, 2026
Copilot stopped work on behalf of
deanhume due to an error
July 2, 2026 08:49
Owner
|
Not merging this change |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Without periodic saves, a crash or unexpected close during a long recording would lose all transcribed content — the summary was only written to the note on Stop.
Changes
LIVE_CHUNK_MS5 000 → 20 000 ms — transcription chunks are now processed and written to the transcript file every 20 seconds.transcriptAppend,refreshSummaryFromFile()is called immediately (live chunks only), so the note's summary block stays current throughout the recording. A crash or unexpected close now loses at most ~20 s of content.force=true) skips the in-chunk refresh;handleRecordingStopcallsrefreshSummaryFromFile()explicitly once the complete transcript is on disk.The ordering guarantees the file is fully written before it is read back for summarisation, matching the intended contract.