Flaky capture smoke: the resumed segment is sometimes missing from the paused recording
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 55/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
Direzione di ricerca
Start with the Windows capture smoke in src/__tests__/captureSmoke.test.ts:93-130, then trace runStop to joinSegments in src/utils/lifecycle.ts and the resume and finalization paths in src/utils/pause.ts and src/utils/recorder.ts. Run RUN_CAPTURE_SMOKE=1 npx vitest run src/__tests__/captureSmoke.test.ts on Windows. Done means failures report segment count, part durations, and join errors, and the root cause is identified with the resumed segment retained or the test waiting until it has frames.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
The Windows CI capture smoke "leaves a paused stretch out of the file and the markers (#200)" fails intermittently, including its retry, and a red run blocks the release. In the failures the stopped recording holds only the first segment, or has a gap over 1 s, so the resumed segment is missing or late in the join.
Where
src/__tests__/captureSmoke.test.ts:93-130(start, 2 s, pause, 3 s, resume, 2 s, stop)- Join path:
src/utils/lifecycle.ts(runStop->joinSegments),src/utils/pause.ts(finishSegments),src/utils/recorder.ts(resume spawn)
Details
Seen on build-and-test (windows-latest, 22) and (windows-latest, 24):
AssertionError: 102 frames over 3.354583s, first segment 3.353s: expected 3.354583 to be greater than 4.353
AssertionError: widest gap 1.367973s; 100 frames over 9.415311s, first segment 3.479s: expected 1.367973 to be less than 1
In the first kind the output is exactly the first segment: the resumed segment contributed no frames, although the test records for 2 s after resume_recording returns. Commits 8a4fad6, e25cc00 and 265975b failed this way; neighbouring commits passed. It did not reproduce locally (3 runs alone and one under the full suite, Windows 11).
Impact
Intermittent red CI on main; per the release flow a red run skips the npm publish. If the resumed segment is really being lost, users lose footage after a pause.
Suggested fix
- Have the test print the stop result's
segments(count and any joinerror) and the per-part durations, so the next failure shows whether the second part is empty, missing or dropped by the join. - Check whether a resumed gdigrab capture that is stopped soon after starting can finalize with zero frames on a slow runner, and whether
joinSegmentsthen silently skips it.
Acceptance criteria
- A failure reports the segment count, part durations and any join error
- Root cause identified; either the join keeps the resumed part or the test waits for it to have frames
Getting started
- Relevant files:
src/__tests__/captureSmoke.test.ts,src/utils/lifecycle.ts,src/utils/pause.ts,src/utils/recorder.ts - How to run tests:
RUN_CAPTURE_SMOKE=1 npx vitest run src/__tests__/captureSmoke.test.tson Windows
Related: #200
Filed by repo-audit/fix-issues at a6cfc9b. Severity: medium. Effort: M. audit-key: testing|src/__tests__/captureSmoke.test.ts|paused-stretch-missing-resume-segment
- Lingua principale
- TypeScript
- Stelle
- 1
- Fork
- 4
- Merge medio
- 14h 8m
- PR unite (30g)
- 48
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di TMHSDigital/screencast-mcp
-
effort: small good first issue priority: medium testing
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
TMHSDigital/screencast-mcp#351 ·
I maintainer di solito rispondono entro 1 giorno
-
bug effort: small priority: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
TMHSDigital/screencast-mcp#344 ·
I maintainer di solito rispondono entro 1 giorno
-
bug effort: small good first issue priority: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
TMHSDigital/screencast-mcp#343 ·
I maintainer di solito rispondono entro 1 giorno
-
effort: medium help wanted priority: medium testing
Difficoltà 3/5 1-2 giorni Idoneità per principianti 76/100
TMHSDigital/screencast-mcp#350 ·
I maintainer di solito rispondono entro 1 giorno
-
effort: medium priority: medium testing
Difficoltà 4/5 1-2 giorni Idoneità per principianti 70/100
TMHSDigital/screencast-mcp#349 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di TMHSDigital/screencast-mcp
Issue simili
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
openclaw/openclaw#200365 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
area-templates triage:bot-seen triage:needs-human
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
microsoft/aspire#22356 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Archiving an agent that is not loaded keeps its old updatedAtForse già presa @luoph l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
content triage
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno