Skip to content

Potential fix for 1 code quality finding #922

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
matteius merged 1 commit into from
Nov 7, 2026
Merged

Potential fix for 1 code quality finding #922

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tests/performance/active-recording.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ descriptors and cumulative native-process CPU ticks once per second. Source
FFmpeg processes share the host; their CPU/memory are not included in the native
process samples. Streams start sequentially before the sampling interval.

After manual stop, every catalogued file must pass ffprobe and full FFmpeg
After the harness automatically stops recordings at the configured duration, every catalogued file must pass ffprobe and full FFmpeg
`-xerror` decoding, with footage present for every stream. Ordinary FFmpeg exit
status alone is insufficient: it can report corrupt frames while exiting zero.
The regression in `mediaLifecycle.api.spec.ts` uses one stream for ten seconds;
Expand Down
Loading