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

V14.12.0 proposal #35285

Merged
merged 73 commits into from
Sep 22, 2020
Merged

V14.12.0 proposal #35285

merged 73 commits into from
Sep 22, 2020

Conversation

ruyadorno
Copy link
Member

@ruyadorno ruyadorno commented Sep 21, 2020

2020-09-22, Version 14.12.0 (Current), @ruyadorno

Notable changes

  • deps:
    • update to uvwasi 0.0.11 (Colin Ihrig) #35104
  • n-api:
    • create N-API version 7 (Gabriel Schulhof) #35199
    • add more property defaults (Gerhard Stoebich) #35214

Commits

cc @nodejs/releasers

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

Trott and others added 30 commits September 17, 2020 10:36
If a bad value is assigned to EventEmitter.defaultMaxListener, a
RangeError is thrown and not a TypeError. Update documentation to
reflect this.

PR-URL: #35069
Reviewed-By: Daijiro Wachi <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
The two starting `Atomics.wait()` operations are not ordered,
but the test assumed a specific ordering because of the latency
that comes with spinning up a Worker thread.

Add variants of the existing potential valid results that account
for the reverse ordering.

Fixes: #35059

PR-URL: #35066
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
This reverts commit 07423b5.

Refs: #35002 (comment)

PR-URL: #35094
Reviewed-By: Mary Marchini <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
We need to emit dependency of ICU's toASCII in order to update the WPT
fixtures. Since ICU and URL isn't the same implementation and they also
follow different specifications. ICU's toASCII shouldn't have a
dependency on WPT fixtures.

Refs: #33770 (comment)
PR-URL: #35077
Reviewed-By: Daijiro Wachi <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Joyee Cheung <[email protected]>
* sort references in ASCII order
* replace abbreviation
* split comma splice into two sentences and add appropriate punctuation
* replace future tense with present tense

PR-URL: #35083
Reviewed-By: Geoffrey Booth <[email protected]>
Reviewed-By: Derek Lewis <[email protected]>
Reviewed-By: Daijiro Wachi <[email protected]>
PR-URL: #35080
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Previously, the crypto.randomInt() message when "max" was less than or
equal to "min" made it sound like the lower bound for "max" was
hard-coded. Make it clear that it is instead dynamic based on the value
of "min".

For crypto.randomInt(10,0):

Before:
RangeError [ERR_OUT_OF_RANGE]: The value of "max" is out of range. It
must be > 10. Received 0

After:

RangeError [ERR_OUT_OF_RANGE]: The value of "max" is out of range. It
must be greater than the value of "min" (10). Received 0

PR-URL: #35088
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Use "must be a safe integer" rather than "must be safe integer". I
believe the former is more easily understood/clear.

PR-URL: #35089
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
This appears to be a remnant from
413d38c.

PR-URL: #35079
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
This improves readability, as well as awkward reptition of the word
_while_ with two different meanings in a single sentence.

Refs: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/w/while

PR-URL: #35078
Reviewed-By: Denys Otrishko <[email protected]>
Reviewed-By: Derek Lewis <[email protected]>
PR-URL: #35065
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Gerhard Stöbich <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
* eliminate unneeded Set deletion/cleanup
* use number of CPUs as limit for processes spawned rather than
  hard-coding the limit

PR-URL: #35101
Reviewed-By: Bradley Farias <[email protected]>
Reviewed-By: Andrey Pechkurov <[email protected]>
Fixes: #35095

PR-URL: #35098
Reviewed-By: Geoffrey Booth <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
PR-URL: #35109
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Franziska Hinkelmann <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
PR-URL: #35111
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Franziska Hinkelmann <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
PR-URL: #35112
Reviewed-By: Franziska Hinkelmann <[email protected]>
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Ricky Zhou <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Derek Lewis <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
PR-URL: #35113
Reviewed-By: Franziska Hinkelmann <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Refs: #35098 (comment)

PR-URL: #35106
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Gerhard Stöbich <[email protected]>
Reviewed-By: Myles Borins <[email protected]>
Reviewed-By: Zeyu Yang <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
PR-URL: #35117
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
- update security process to reflect current way
  to request tweet/retweet of security release

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: #35107
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: Ash Cripps <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Notable changes:

- Several issues have been addressed in uvwasi_fd_readdir().
  A bug in the copying of the directory entry's name has been fixed.
  The function now returns UVWASI_ENOSYS on Windows and Android.
  Serdes support has been added for uvwasi_dirent_t's.
- The libuv dependency has been updated to v1.39.0.

PR-URL: #35104
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Update email address to reflect move to
Red Hat

Signed-off-by: Michael Dawson <[email protected]>

PR-URL: #35121
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Gireesh Punathil <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Because of the condition that starts the `if` block, we know that
`parentPath` must be truthy. So there is no need to check for that in
the template string that generates the error message.

PR-URL: #35123
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Juan José Arboleda <[email protected]>
Reviewed-By: Guy Bedford <[email protected]>
PR-URL: #35126
Reviewed-By: Michael Dawson <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Fixes: #31037

PR-URL: #34835
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Ricky Zhou <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
PR-URL: #35160
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Mary Marchini <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
PR-URL: #35134
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Yongsheng Zhang <[email protected]>
PR-URL: #35138
Fixes: #34561
Reviewed-By: Ricky Zhou <[email protected]>
Reviewed-By: Robert Nagy <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Zeyu Yang <[email protected]>
PR-URL: #35139
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Mary Marchini <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>
Reviewed-By: Zeyu Yang <[email protected]>
Reviewed-By: Daijiro Wachi <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
@nodejs-github-bot

This comment has been minimized.

Trott and others added 2 commits September 21, 2020 21:23
Error messages are a mix of present and past tense. They should be
mostly or entirely present tense. This eliminates the past tense
constructions "was found" and "were found".

Backport-PR-URL: #35247
PR-URL: #35164
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Denys Otrishko <[email protected]>
Reviewed-By: Derek Lewis <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Notable changes:

- deps:
  - update to uvwasi 0.0.11 (Colin Ihrig)
  [#35104](#35104)
- n-api:
  - create N-API version 7 (Gabriel Schulhof)
  [#35199](#35199)
  - add more property defaults (Gerhard Stoebich)
  [#35214](#35214)

PR-URL: #35285
@nodejs-github-bot

This comment has been minimized.

@lpinca
Copy link
Member

lpinca commented Sep 22, 2020

Can #34015 or just 4b3654e be backported? See websockets/ws#1795.

cc: @benjamingr @jasnell

@targos
Copy link
Member

targos commented Sep 22, 2020

@lpinca it's supposed to be in v14.5.0: #34093

@lpinca
Copy link
Member

lpinca commented Sep 22, 2020

@targos yes but the issue is on Node.js 12. Node.js 14 is ok. I wonder if the event target fixes will ever be backported to Node.js 12.

@targos
Copy link
Member

targos commented Sep 22, 2020

Ok, I understand what you're asking for, but this release proposal is for Node.js 14.

@lpinca
Copy link
Member

lpinca commented Sep 22, 2020

Oh wow, sorry. I have not fully woken up yet.

@aduh95
Copy link
Contributor

aduh95 commented Sep 22, 2020

It would be great to have #35191 as it fixes a few broken links in the docs.

@nodejs-github-bot

This comment has been minimized.

@nodejs-github-bot
Copy link
Collaborator

nodejs-github-bot commented Sep 22, 2020

@ruyadorno
Copy link
Member Author

hi @aduh95 sorry but I think it's a bit too late for that one to land in time for this release 😊

Copy link
Contributor

@MylesBorins MylesBorins left a comment

Choose a reason for hiding this comment

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

LGTM

Reviewed CITGM and the new failures are unrelated to this release

@ruyadorno ruyadorno merged commit efd5c83 into v14.x Sep 22, 2020
ruyadorno added a commit that referenced this pull request Sep 22, 2020
ruyadorno added a commit that referenced this pull request Sep 22, 2020
Notable changes:

- deps:
  - update to uvwasi 0.0.11 (Colin Ihrig)
  [#35104](#35104)
- n-api:
  - create N-API version 7 (Gabriel Schulhof)
  [#35199](#35199)
  - add more property defaults (Gerhard Stoebich)
  [#35214](#35214)

PR-URL: #35285
ruyadorno added a commit to ruyadorno/nodejs.org that referenced this pull request Sep 22, 2020
@ruyadorno ruyadorno deleted the v14.12.0-proposal branch September 22, 2020 18:27
MylesBorins pushed a commit to nodejs/nodejs.org that referenced this pull request Sep 22, 2020
joesepi pushed a commit to joesepi/node that referenced this pull request Jan 8, 2021
Notable changes:

- deps:
  - update to uvwasi 0.0.11 (Colin Ihrig)
  [nodejs#35104](nodejs#35104)
- n-api:
  - create N-API version 7 (Gabriel Schulhof)
  [nodejs#35199](nodejs#35199)
  - add more property defaults (Gerhard Stoebich)
  [nodejs#35214](nodejs#35214)

PR-URL: nodejs#35285
@targos targos added release Issues and PRs related to Node.js releases. and removed doc Issues and PRs related to the documentations. meta Issues and PRs related to the general management of the project. wasi Issues and PRs related to the WebAssembly System Interface. labels Jun 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Issues and PRs related to Node.js releases.
Projects
None yet
Development

Successfully merging this pull request may close these issues.