fix: import Packet for subgraph EOF handling - #220
Merged
Conversation
sfeiwong
approved these changes
Aug 25, 2026
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
2 participants
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
PacketwhereSubGraph.process()creates downstream EOF packetsFixes #219.
Validation
SubGraph.process()EOF-path regression: passedruff check --select E9,F63,F7,F82: passedgit diff --check: passedThe full native BMF test suite was not run locally because this Windows environment does not have the repository's BMF native build artifacts, compiler/CMake toolchain, or supported FFmpeg 4.x/5.x SDK. The added test is colocated with the existing subgraph integration tests for execution in a built development environment.