GeezerVison is showing github.com — v19.2.0 proposal by ruyadorno · Pull Request #45615 · nodejs/node
Conversation
ruyadorno
commented
Nov 24, 2022
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
2022-11-29, Version 19.2.0 (Current), @ruyadorno
Notable changes
Time zone update
Time zone data has been updated to 2022f. This includes changes to Daylight Savings Time (DST) for Fiji and Mexico. For more information, see https://mm.icann.org/pipermail/tz-announce/2022-October/000075.html.
Other notable changes
- buffer
- (SEMVER-MINOR) introduce
File class (Khafra) #45139
- deps
- update V8 to 10.8.168.20 (Michaël Zasso) #45230
- doc
- deprecate use of invalid ports in
url.parse (Antoine du Hamel) #45576
- util
- add fast path for utf8 encoding (Yagiz Nizipli) #45412
Commits
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
bricss, viniciusalvesmello, and manekinekko reacted with thumbs up emoji
KhafraDev, bricss, and viniciusalvesmello reacted with hooray emoji
bricss, ThiagodePaulaSouza, and viniciusalvesmello reacted with heart emoji
bricss and viniciusalvesmello reacted with rocket emoji
All reactions
-
👍
3 reactions
-
🎉
3 reactions
-
❤️
3 reactions
-
🚀
2 reactions
Currently, there's no way to know if a timezone upgrade PR is correct
without building and testing the change locally. This change provides a
solution for that.
Tested in RaisinTen#4.
Signed-off-by: Darshan Sen <[email protected]>
PR-URL: #45299
Reviewed-By: Antoine du Hamel <[email protected]>
Original commit message:
[runtime] Clear array join stack when throwing uncatchable
... exception.
Array#join depends array_join_stack to avoid infinite loop
and ensures symmetric pushes/pops through catch blocks to
correctly maintain the elements in the join stack.
However, the stack does not pop the elements and leaves in
an invalid state when throwing the uncatchable termination
exception. And the invalid join stack state will affect
subsequent Array#join calls. Because all the terminate
exception will be handled by Isolate::UnwindAndFindHandler,
we could clear the array join stack when unwinding the terminate
exception.
Bug: v8:13259
Change-Id: I23823e823c5fe0b089528c5cf654864cea78ebeb
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3878451
Reviewed-by: Jakob Linke <[email protected]>
Commit-Queue: 王澳 <[email protected]>
Cr-Commit-Position: refs/heads/main@{#83465}
Refs: v8/v8@031b98b
Closes: #44417
PR-URL: #45375
Fixes: #44417
Reviewed-By: Jiawen Geng <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Reviewed-By: Kohei Ueno <[email protected]>
Remove explicit setting of configuration options in rules when those
options are the defaults.
PR-URL: #45397
Reviewed-By: Joyee Cheung <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
When encountering ERR_UNESCAPED_CHARACTERS on large applications it can
be unclear which request has caused this error. Even when setting
NODE_DEBUG=http there is no information about this error since it's
thrown before any debug logs. This patch adds a debug log that contains
the invalid path.
PR-URL: #45420
Reviewed-By: Matteo Collina <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Add hook to AsyncLocalStorage to allow user to stop propagation.
This is needed to avoid leaking a store if e.g. the store indicates
that its operations are finished or it reached its time to live.
PR-URL: #45386
Reviewed-By: Stephen Belanger <[email protected]>
Reviewed-By: Minwoo Jung <[email protected]>
Reviewed-By: Chengzhong Wu <[email protected]>
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Maybe it's not too late to pull #45537, #45592 and #45573? 🤔
Sorry, not adding anything new at this point 😊
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Is there any documentation referenced regarding critical security vulnerability releases outside the normal release cycle?
https://nvd.nist.gov/vuln/detail/CVE-2022-37434
I'm looking for a rough timeline of when I can tell my internal customers their critical vulnerability scans can be resolved.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
ruyadorno
added a commit
that referenced
this pull request
Nov 29, 2022
Notable changes:
buffer:
* (SEMVER-MINOR) introduce File (Khafra) #45139
deps:
* update timezone to 2022f (Node.js GitHub Bot) #45289
* update V8 to 10.8.168.20 (Michaël Zasso) #45230
doc:
* deprecate use of invalid ports in `url.parse` (Antoine du Hamel) #45576
util:
* add fast path for utf8 encoding (Yagiz Nizipli) #45412
PR-URL: #45615
This was referenced Dec 1, 2022
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Labels
release
Issues and PRs related to Node.js releases.
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.
|