chore(WebSocketShard): improve zlib-sync errors #10808
Open
+18
−4
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
Qjuh
approved these changes
May 2, 2025
almeidx
reviewed
May 2, 2025
|
I can't reproduce that test failure locally, not sure what happened there? |
almeidx
requested changes
May 28, 2025
| @@ -31,6 +32,17 @@ export const CompressionParameterMap = { | |||
| [CompressionMethod.ZlibSync]: 'zlib-stream', | |||
| } as const satisfies Record<CompressionMethod, string>; | |||
|
|
|||
| export const ZlibErrorCodes = { | |||
| [ZlibSync.Z_NEED_DICT]: 'Z_NEED_DICT', | |||
There was a problem hiding this comment.
Can't import zlib-sync on the top level at runtime. It's being lazy loaded conditionally since it's usage is opt-in
Refer to the parenthesis i included in #10808 (comment)
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.
Please describe the changes this PR makes and why it should be merged:
The current error thrown from
zlib-syncisn't great, and doesn't match what errors fromnode:zliblook like. This brings them more in line withnode:zliberrors.Status and versioning classification: