Flaky capture smoke: the resumed segment is sometimes missing from the paused recording
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 55/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- TypeScript
- Estrellas
- 1
- Forks
- 4
- Merge medio
- 14 h 8 min
- PR fusionados (30 d)
- 48
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de TMHSDigital/screencast-mcp
-
effort: small good first issue priority: medium testing
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
TMHSDigital/screencast-mcp#351 ·
Los mantenedores suelen responder en 1 día
-
bug effort: small priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
TMHSDigital/screencast-mcp#344 ·
Los mantenedores suelen responder en 1 día
-
bug effort: small good first issue priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
TMHSDigital/screencast-mcp#343 ·
Los mantenedores suelen responder en 1 día
-
effort: medium help wanted priority: medium testing
Dificultad 3/5 1-2 días Aptitud para principiantes 76/100
TMHSDigital/screencast-mcp#350 ·
Los mantenedores suelen responder en 1 día
-
effort: medium priority: medium testing
Dificultad 4/5 1-2 días Aptitud para principiantes 70/100
TMHSDigital/screencast-mcp#349 ·
Los mantenedores suelen responder en 1 día
Todos los issues de TMHSDigital/screencast-mcp
Issues similares
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
openclaw/openclaw#200365 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
area-templates triage:bot-seen triage:needs-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
microsoft/aspire#22356 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Archiving an agent that is not loaded keeps its old updatedAtPosiblemente ocupada @luoph la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
content triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día