Propagate error from zipfile to the caller of read()#319175
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR improves ZIP reading error reporting by ensuring yauzl/ZipFile errors are propagated back to callers of read() (and therefore buffer()), which is relevant to extension installation flows that need clearer diagnostics for corrupt/truncated VSIX downloads.
Changes:
- Attach a
zipfile-level'error'listener inread()so the returned promise can reject when the underlying ZIP parser fails.
Show a summary per file
| File | Description |
|---|---|
| src/vs/base/node/zip.ts | Adds propagation of ZipFile error events from read() to its returned promise. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 1
TylerLeonhardt
approved these changes
May 30, 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
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.
This will make errors like #314359 be reported more nicely.