Remove legacy ffmpeg frame fallback - #69
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: fe68a1a8-e1d5-408b-b178-b3b4136f1490
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why remove instead of time out
Captured-frame manifests have shipped in every tagged release since v0.1.0. Keeping the fallback would add timeout, process-kill, partial-output cleanup, and test-injection machinery solely for unreleased development-era sessions. Removing it eliminates both the indefinite hang in #14 and the orphaned partial-output path tracked in #11 (L6).
Testing
npm run typechecknpm test: 176 passednpm run buildCloses #14.