Disarming a triggered recording while it starts says "nothing was recorded", but the recording starts
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 78/100
- Issue-Typ
- Bug
- Klarheit
- Klar beschrieben
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- node.js, typescript
Rechercherichtung
Read src/utils/triggers.ts around disarm and armStart, then inspect the disarm branch in src/tools/stopRecording.ts and the trigger tests in src/__tests__/triggers.test.ts. Run npm test to see the existing behavior. Add a delayed fake fire test; done means stopping during startup leaves no live session and the response accurately reports that the session was stopped.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Summary
When startWhen fires, armStart runs the whole start (await o.fire()) while the arm's status is still "armed". A stop_recording on the arm id during that window takes the disarm branch and reports cancelled / "Disarmed; nothing was recorded.", but the start then finishes and a recording runs until its cap.
Where
src/utils/triggers.ts:59-65(disarmonly checksstatus !== "armed")src/utils/triggers.ts:147-151(fire()awaited without changing status, thenstatus = "started")src/tools/stopRecording.ts:86-90(disarm branch)src/tools/startRecording.ts:489(the fired start runs the full handler: target resolution, event logger, encoder probe, settle)
Impact
The agent and the user are told the armed capture was cancelled and nothing was recorded, while the screen (and the input-event log if requested) is recorded a moment later for up to the cap (default 1 h). Nothing in the response shows that a session exists.
Steps to reproduce
start_recording {"target":"full","startWhen":{"window":"window:Notepad"},"events":true}- Open Notepad, and within 1-3 s (while the start runs) call
stop_recording {"sessionId":"arm-..."}. The response isstatus: "cancelled". - A few seconds later,
list_sessionsshows a newrecordingsession.
Suggested fix
Set a distinct status (e.g. "starting") before await o.fire(). In stop_recording, for a "starting" arm, record a cancel request that armStart honours by stopping the session as soon as fire returns (or await the fire's promise and then stop the session). Report "nothing was recorded" only for an arm that was still waiting.
Acceptance criteria
- Stopping an arm whose start is in progress stops the session it produces, and the response says so.
- Test with a fake
firethat resolves after a delay: stop during the delay leaves no live session.
Getting started
- Relevant files:
src/utils/triggers.ts,src/tools/stopRecording.ts,src/__tests__/triggers.test.ts - How to run tests:
npm test
Filed by repo-audit/full-audit at b9b94fa. Severity: medium. Effort: S. audit-key: bug|src/utils/triggers.ts|armStart
- Vorherrschende Sprache
- TypeScript
- Sterne
- 1
- Forks
- 4
- Ø Merge
- 14 Std. 8 Min.
- Gemergte PRs (30 T.)
- 48
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus TMHSDigital/screencast-mcp
-
effort: small good first issue priority: medium testing
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
TMHSDigital/screencast-mcp#351 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug effort: small priority: medium
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
TMHSDigital/screencast-mcp#344 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug effort: small good first issue priority: medium
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
TMHSDigital/screencast-mcp#343 ·
Maintainer antworten meist innerhalb von 1 Tag
-
effort: medium help wanted priority: medium testing
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 76/100
TMHSDigital/screencast-mcp#350 ·
Maintainer antworten meist innerhalb von 1 Tag
-
effort: medium priority: medium testing
Schwierigkeit 4/5 1-2 Tage Anfängerfreundlichkeit 70/100
TMHSDigital/screencast-mcp#349 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in TMHSDigital/screencast-mcp
Ähnliche Issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
openclaw/openclaw#200365 · 1 Kommentar · 1 Reaktion ·
Maintainer antworten meist innerhalb von 1 Tag
-
area-templates triage:bot-seen triage:needs-human
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
microsoft/aspire#22356 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Archiving an agent that is not loaded keeps its old updatedAtEvtl. vergeben @luoph hat das heute übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Maintainer antworten meist innerhalb von 1 Tag
-
content triage
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 88/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag