Skip to content
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

doc: minor issues #13491

Conversation

tniessen
Copy link
Member

@tniessen tniessen commented Jun 6, 2017

Fixes most of the points suggested in #9538. Some have already been fixed, and I consider some of the others irrelevant. I am not sure about points 7, 8 and 16, though.

I did not notice another PR #9703 already worked on this without being merged until I pushed my commits. Apparently there was no activity for almost half a year, but feel free to close this PR if you think we should wait for the other one to get back to life.

Checklist
Affected core subsystem(s)

doc

@nodejs-github-bot nodejs-github-bot added the doc Issues and PRs related to the documentations. label Jun 6, 2017
doc/api/vm.md Outdated
@@ -129,7 +129,7 @@ console.log(util.inspect(sandbox));
event loops and corresponding threads being started, which have a non-zero
performance overhead.

### script.runInNewContext([sandbox][, options])
### script.runInNewContext(sandbox[, options])
Copy link
Contributor

Choose a reason for hiding this comment

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

This isn't correct. It should probably instead be: [sandbox[, options]]

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks, fixed.

Copy link
Contributor

Choose a reason for hiding this comment

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

@tniessen: what @mscdex suggested, and what you finally did are different. AFAICT from a quick look at the source (and knowing nothing about vm), his syntax is correct and yours is not quite.

@@ -1250,7 +1250,7 @@ This is an important security release. All Node.js users should consult the secu
- Add support for Intel's VTune JIT profiling when compiled with `--enable-vtune-profiling`. For more information about VTune, see <https://software.intel.com/en-us/node/544211>. (Chunyang Dai) [#3785](https://github.com/nodejs/node/pull/3785).
- Properly enable V8 snapshots by default. Due to a configuration error, snapshots have been kept off by default when the intention is for the feature to be enabled. (Fedor Indutny) [#3962](https://github.com/nodejs/node/pull/3962).
* **crypto**:
- Simplify use of ECDH (Elliptic Curve Diffie-Hellman) objects (created via `crypto.createECDH(curve_name)`) with private keys that are not dynamically generated via `generateKeys()`. The public key is now computed when explicitly setting a private key. Added validity checks to reduce the possibility of computing weak or invalid shared secrets. Also, deprecated the `setPublicKey()` method for ECDH objects as its usage is unnecessary and can lead to inconsistent state. (Michael Ruddy) [#3511](https://github.com/nodejs/node/pull/3511).
- Simplify use of ECDH (Elliptic Curve Diffie-Hellman) objects (created via `crypto.createECDH(curveName)`) with private keys that are not dynamically generated via `generateKeys()`. The public key is now computed when explicitly setting a private key. Added validity checks to reduce the possibility of computing weak or invalid shared secrets. Also, deprecated the `setPublicKey()` method for ECDH objects as its usage is unnecessary and can lead to inconsistent state. (Michael Ruddy) [#3511](https://github.com/nodejs/node/pull/3511).
Copy link
Member

Choose a reason for hiding this comment

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

Why this change?

Copy link
Member Author

Choose a reason for hiding this comment

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

It's not strictly necessary, just for consistency.

Copy link
Member

Choose a reason for hiding this comment

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

I'd prefer to avoid changes to the changelog unless necessary

Copy link
Member Author

Choose a reason for hiding this comment

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

That sounds reasonable, fixed, PTAL.

@tniessen
Copy link
Member Author

cc @nodejs/documentation

@tniessen tniessen force-pushed the knock-knock-whos-there-its-a-minor-issue-in-the-docs branch from 2a72a88 to 456b91f Compare June 13, 2017 20:31
Copy link
Contributor

@sam-github sam-github left a comment

Choose a reason for hiding this comment

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

Other than that #13491 (comment) did not get quite addressed, this looks good to me.

@tniessen tniessen force-pushed the knock-knock-whos-there-its-a-minor-issue-in-the-docs branch from 456b91f to 0ec2d65 Compare June 13, 2017 21:34
@tniessen
Copy link
Member Author

@sam-github My bad, I actually fixed it but dropped the commit when I fixed this comment. PTAL.

tniessen added a commit that referenced this pull request Jun 13, 2017
oath.md: make order of properties consistent
tls.md: remove spaces in getPeerCertificate signature
tls.md: add deprecation notice to server.connections
http.md: fix signature of request.end
crypto.md: change crypto parameters to camelCase
vm.md: add missing apostrophe
vm.md: fix signature of vm.runInNewContext
zlib.md: improve description of zlib.createXYZ

PR-URL: #13491
Ref: #9538
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@tniessen
Copy link
Member Author

Landed in e318c8a

@tniessen tniessen closed this Jun 13, 2017
@sam-github
Copy link
Contributor

FWIW, I would not have squashed before landing, each commit fixed completely independent problems.

@tniessen
Copy link
Member Author

tniessen commented Jun 13, 2017

Sorry, thought we had discussed that in IRC (@refack).

@sam-github
Copy link
Contributor

so did I :-)

[2017-06-13 14:04] last line of that comment: "I think a single big PR is acceptable as long as it's broken up in logical commits, i.e., one fix per commit."

@tniessen
Copy link
Member Author

tniessen commented Jun 13, 2017

To put that statement into context:

tniessen: I am not sure whether I should merge #13491 as a single commit or as multiple. Usually we squash them together but ben and sam requested multiple commits, at least during PR phase: #9538 (comment)
refack: wrong link?
tniessen: last line of that comment: "I think a single big PR is acceptable as long as it's broken up in logical commits, i.e., one fix per commit."
tniessen: PR: #13491
refack: IMHO just during PR
refack: for easier review

Must have misinterpreted your messages (after that ⬆️), sorry.
I will keep it in mind for the next time. If you want to, I can force-push the individual commits.

@sam-github
Copy link
Contributor

Don't worry, at least it landed with commit meta data, and I'm sure some of mine have missed that. Just for next time.

@refack
Copy link
Contributor

refack commented Jun 13, 2017

Must have misinterpreted your messages (after that ⬆️), sorry.
I will keep it in mind for the next time. If you want to, I can force-push the individual commits.

I also misinterpreted 🤷‍♂️

addaleax pushed a commit that referenced this pull request Jun 17, 2017
oath.md: make order of properties consistent
tls.md: remove spaces in getPeerCertificate signature
tls.md: add deprecation notice to server.connections
http.md: fix signature of request.end
crypto.md: change crypto parameters to camelCase
vm.md: add missing apostrophe
vm.md: fix signature of vm.runInNewContext
zlib.md: improve description of zlib.createXYZ

PR-URL: #13491
Ref: #9538
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@addaleax addaleax mentioned this pull request Jun 17, 2017
addaleax pushed a commit that referenced this pull request Jun 21, 2017
oath.md: make order of properties consistent
tls.md: remove spaces in getPeerCertificate signature
tls.md: add deprecation notice to server.connections
http.md: fix signature of request.end
crypto.md: change crypto parameters to camelCase
vm.md: add missing apostrophe
vm.md: fix signature of vm.runInNewContext
zlib.md: improve description of zlib.createXYZ

PR-URL: #13491
Ref: #9538
Reviewed-By: Sam Roberts <vieuxtech@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
@addaleax addaleax mentioned this pull request Jun 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants