[codex] Fix Home summary notice dismissal#1128
Merged
Merged
Conversation
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.
Summary
Repro signal
The June 8 self-sent
Transcripted Feedbackemail showedmeeting.local_meeting_summary_completedwithchunk_count=1, while the greenAI summary savedHome notice stayed on screen. That points at the Home notice lifecycle after completion, not the Gemma generation path itself.Nearby follow-up
The same report also says Gemma setup can show ready while Home remains in
Generating AI summaryfor a long time. I kept this PR scoped to the stuck saved notice; that slower generating state should be handled separately.Verification
bash run-tests.sh --filter HomeMeetingSummaryBetaPresentationPolicyTestsbash build-deps.sh --forcebash build.sh --no-openbash run-tests.sh