Skip to content

fix: restore interrupted audio and show upcoming set weight - #10

Merged
lagrangee merged 1 commit into
mainfrom
codex/fix-audio-recovery-rest-weight
Sep 22, 2026
Merged

lagrangee merged 1 commit into
mainfrom
codex/fix-audio-recovery-rest-weight

Conversation

@lagrangee

@lagrangee lagrangee commented Sep 22, 2026

Copy link
Copy Markdown
Owner

Switching apps or locking the screen could leave countdown cues silent even after explicit resume because the browser audio output reused an interrupted AudioContext. Retire that context on visibility loss/pagehide (including already-paused Sessions), activate fresh output in the next user gesture, and reschedule only the remaining cues. Ignore late activation success from the retired context and reuse decoded cue buffers.

The rest screen now shows the upcoming Prescribed Set's resistance alongside its target, including kg per implement, implement quantity, and bodyweight. It uses the same snapshot lookup and formatting as the active exercise.

Validation:

  • Reproduced the missing weight and silent-output lifecycle regressions before the fix.
  • Focused Vue/timeline/Session tests: 80 passed, covering visibility loss, pagehide/BFCache, already-paused interruption, stuck old resume, and canonical/legacy resistance formats.
  • npm run check passed (374 passed, 1 optional test skipped).
  • Chromium with synthetic data at 390×844 and 1280×900: upcoming weight displayed; explicit resume closed old audio output and started a fresh advancing context; no application console errors.
  • npm run release-check passed in an isolated checkout of the exact commit (including 228 UI tests, Chromium smoke, coverage and public-source privacy checks).

Contract impact: clarify existing Session interruption behavior and rest-preview snapshot semantics; no API shape, database migration, or training-data changes. Real-device iOS lock-screen audibility is not established by the automated checks.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 22, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-22T15:45:18.855345Z 136469a PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@lagrangee
lagrangee merged commit 285e72c into main Sep 22, 2026
1 check passed
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