-
-
Notifications
You must be signed in to change notification settings - Fork 31.6k
zlib: add error handling for trailing junk after stream end #58316
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.
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
Open
0hmX
wants to merge
3
commits into
nodejs:main
Choose a base branch
from
0hmX:DecompressionStream
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+83
−10
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
138710a
to
002c166
Compare
Introduce `ERR_TRAILING_JUNK_AFTER_STREAM_END` error to handle unexpected data after the end of a compressed stream. This ensures proper error reporting when decompressing deflate or gzip streams with trailing junk. Added tests to verify the behavior. Fixes: nodejs#58247
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #58316 +/- ##
==========================================
+ Coverage 90.18% 90.23% +0.04%
==========================================
Files 629 633 +4
Lines 186641 186845 +204
Branches 36654 36680 +26
==========================================
+ Hits 168329 168599 +270
+ Misses 11112 11042 -70
- Partials 7200 7204 +4
🚀 New features to boost your workflow:
|
…ive.any.js All subtests in decompression-corrupt input.tentative.any.js now pass, so the "fail.expected" entry has been removed from the status file. This reflects the current passing state of the test suite.
Corrected the formatting of the `ERR_TRAILING_JUNK_AFTER_STREAM_END` section by removing trailing spaces and ensuring consistent line breaks for better readability.
cc: @nodejs/zlib |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
errors
Issues and PRs related to JavaScript errors originated in Node.js core.
needs-ci
PRs that need a full CI run.
web streams
zlib
Issues and PRs related to the zlib subsystem.
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.
Close #58247
Introduce
ERR_TRAILING_JUNK_AFTER_STREAM_END
error to handle unexpected data after the end of a compressed stream. This ensures proper error reporting when decompressing deflate or gzip streams with trailing junk. Added tests to verify the behavior.