Skip to content

[fix] a stopped meeting's cockpit never shows the tree, and one with no report goes Home - #574

Merged
YJack0000 merged 1 commit into
mainfrom
fix/stop-without-report
Oct 4, 2026
Merged

YJack0000 merged 1 commit into
mainfrom
fix/stop-without-report

Conversation

@YJack0000

Copy link
Copy Markdown
Contributor

What this changes

A stopped meeting's cockpit never shows the left tree, and a meeting that ends without a report goes Home with a message saying why.

Why

#543 (v0.32.1) held the tree back only while the save was in flight. A meeting that ended without a report — too short for Rust to keep, or nothing transcribed — cleared the finalizing flag and stayed on its cockpit, so the tree came back beside the three coach columns: the four-column frame again. Reproduced from a user's log (2026-10-04 23:21): a 2-second start/stop whose only line was still a partial → history: live save skipped (no transcript) → stuck on a four-column cockpit.

How

  • cockpitHold replaces finalizingHold (lib/shell/sidebar.ts): the tree stays hidden for as long as a stopped meeting's cockpit is on screen, whatever the save is doing. ⌘B still peeks without touching the saved preference.
  • leaveStoppedCockpit (lib/history/history.ts): a recording Rust discarded (too short) or a live save skipped for no transcript goes Home with a toast (meeting.notSaved.tooShort / .noTranscript), unless the user has already moved on or started another meeting.
  • A failed save stays on the cockpit — its transcript is the only copy on screen — and now shows an error toast (meeting.notSaved.failed) instead of looking like a slow save.

How it was verified

  • bunx tsc --noEmit passes
  • bunx vitest run passes (791)
  • Browser harness, the exact reported state (stopped, not finalizing, live route): 3 panels and no tree; leaveStoppedCockpit lands on Home with the tree and the toast. Tauri app end-to-end not yet run.
  • Tests: sidebar.test.ts rewritten for the cockpit hold, history.test.ts covers leaveStoppedCockpit
  • New strings in both zh-TW and en

Refs #544.

…no report goes Home

v0.32.1 held the tree back only while the save was in flight. A meeting that
ended without a report (too short for Rust to keep, or nothing transcribed,
e.g. a 2-second start/stop whose only line was still partial) cleared the
finalizing flag and stayed on its cockpit, so the tree came back beside the
coach: the four-column frame again.

- cockpitHold replaces finalizingHold: the tree stays hidden for as long as a
  stopped meeting's cockpit is on screen, whatever the save is doing. Cmd+B
  still peeks.
- leaveStoppedCockpit: a discarded recording (Rust) or a skipped save (no
  transcript) goes Home with a toast saying why, unless the user already
  moved on or started another meeting.
- A failed save stays on the cockpit (its transcript is the only copy on
  screen) and now shows an error toast instead of looking like a slow save.
@github-actions

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown

✅ SonarQube Quality Gate passed — pathorsAI_parley

0 open issues on this PR.

@YJack0000
YJack0000 merged commit b926fcb into main Oct 4, 2026
4 checks passed
@YJack0000
YJack0000 deleted the fix/stop-without-report branch October 4, 2026 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant