Conversation
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.
Opening a TAR archive currently retains every expanded file body before callers can inspect entries or enforce their own limits. Add
OpenStreamandOpenStreamByteswith sequentialNext,Read, andCloseoperations across all supported formats.Apply input, per-entry, expanded-byte, and entry-count limits before exposing bodies. TAR and gem consume forward-only input; ZIP and conda buffer compressed input or reuse the slice passed to
OpenStreamBytes. Expanded bodies are processed one at a time.Preserve paths, modes, duplicate entries, and TAR link metadata so consumers such as
swhid-gocan hash streamed content and build directory identities. Document input ownership, decoder memory overhead, and TAR trailer validation limits.