Skip to content

zlib: warn before crash on invalid internals usage #16657

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.

Sign up for GitHub

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

Closed
addaleax wants to merge 3 commits into from
Closed

zlib: warn before crash on invalid internals usage #16657

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0f3e3e5
zlib: warn before crash on invalid internals usage
addaleax Oct 31, 2017
87885e7
[squash] nit
addaleax Nov 1, 2017
7903320
[squash] nit
addaleax Nov 1, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
[squash] nit
  • Loading branch information
@addaleax
addaleax committed Nov 1, 2017
commit 87885e76e24b5cfda6f86a1085f9fa953be2fe60
2 changes: 1 addition & 1 deletion src/node_zlib.cc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -430,7 +430,7 @@ class ZCtx : public AsyncWrap {
"uses the internals of Node.js in an invalid way.\nPlease use "
Copy link
Copy Markdown
Member

@Trott Trott Nov 1, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Micro-nit (totally not blocking): s/uses the internals of Node.js in an invalid way/is incompatible with this version of Node.js/

Copy link
Copy Markdown
Member Author

@addaleax addaleax Nov 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I prefer the current wording because it gives more of a hint on why the error is occurring. That the versions are incompatible kind of follows from the rest of the message, right?

Copy link
Copy Markdown
Member

@Trott Trott Nov 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I'm trying to avoid "uses the internals of Node.js in an invalid way" as it seems likely to be seen as throwing a bit of shade at npm. But I may be overthinking it.

Beyond that, my thinking was that the user needs to know the versions are incompatible, and why (or whose responsible for the situation) are secondary.

All that said, I'm fine with the current wording.

Copy link
Copy Markdown
Member Author

@addaleax addaleax Nov 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Trott yup, updated!

"either the version of npm that is bundled with Node.js, or "
"a version of npm (> 5.5.1 or < 5.4.0) or node-tar (> 4.0.1) "
"that is compatible with Node 9 and above.\n");
"that is compatible with Node.js 9 and above.\n");
}
CHECK(args.Length() == 7 &&
"init(windowBits, level, memLevel, strategy, writeResult, writeCallback,"
Expand Down