-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
transform streams: unpipe or ignore future writes after .push(null) #64
Closed
jonathanong opened this issue
Dec 4, 2014
· 2 comments
· May be fixed by solebox/node#24, UbuntuEvangelist/node#15, erdun/node#39, enterstudio/node#23 or s4sc/node#23
Closed
transform streams: unpipe or ignore future writes after .push(null) #64
jonathanong opened this issue
Dec 4, 2014
· 2 comments
· May be fixed by solebox/node#24, UbuntuEvangelist/node#15, erdun/node#39, enterstudio/node#23 or s4sc/node#23
Comments
👍 , def. looks like a bug to me |
Keeping this discussion in original issue. |
kunalspathak
referenced
this issue
in nodejs/node-chakracore
Dec 7, 2015
chakrashim: Code cleanup Reviewed most of the CHAKRA-TODO for error handling and updated the code accordingly. Removed these comments from the code. Minor clean up to undo the @eb3d8ba now Chakra propagates the OOM errors. Converted keepalive property name to symbols.
mmarchini
pushed a commit
that referenced
this issue
Jun 5, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jun 7, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jun 9, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jun 10, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jun 16, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jun 19, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jul 2, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jul 13, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jul 21, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jul 23, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jul 24, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jul 25, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jul 25, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jul 26, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Jul 29, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Aug 4, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Aug 7, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
targos
pushed a commit
that referenced
this issue
Aug 11, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: #64
devsnek
pushed a commit
to devsnek/node
that referenced
this issue
Aug 15, 2018
This commit updates the following postmortem metadata constant: - v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__int - Renamed: v8dbg_class_SharedFunctionInfo__internal_formal_parameter_count__uint16_t - V8 commit: v8/v8@53d4dfc Fixes: nodejs#64
targos
added a commit
to targos/node
that referenced
this issue
Apr 17, 2021
Original commit message: Reland "[regexp] Hard-crash on invalid offsets in AdvanceCurrentPosition" This is a reland of 164cf80bbb0a6e091300bfc4cbbe70a6e6bd3e49 The reland fixes UB (left-shift of negative integer type) with a static_cast<uint32_t>. Original change's description: > [regexp] Hard-crash on invalid offsets in AdvanceCurrentPosition > > Drive-by: Range checks in `Emit(byte, twenty_four_bits)` to ensure the > given packed bits actually fit into 24 bits. > > Bug: chromium:1166138 > Change-Id: I2e711e6466bb48d7b9897f68dfe621d12bd92508 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2625877 > Commit-Queue: Jakob Gruber <jgruber@chromium.org> > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Auto-Submit: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/master@{#72064} (cherry picked from commit ff8d0f92d423774cf773b5b4fb48b6744971e27a) No-Try: true No-Presubmit: true No-Tree-Checks: true Tbr: leszeks@chromium.org Bug: chromium:1166138 Change-Id: I514495e14bb99dfc9588fdb4a9f35d67d8d64acb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2626663 Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#72088} Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2742954 Reviewed-by: Jana Grill <janagrill@chromium.org> Commit-Queue: Victor-Gabriel Savu <vsavu@google.com> Cr-Commit-Position: refs/branch-heads/8.6@{nodejs#64} Cr-Branched-From: a64aed2333abf49e494d2a5ce24bbd14fff19f60-refs/heads/8.6.395@{#1} Cr-Branched-From: a626bc036236c9bf92ac7b87dc40c9e538b087e3-refs/heads/master@{#69472} Refs: v8/v8@53c4d05
targos
added a commit
to targos/node
that referenced
this issue
Apr 27, 2021
Original commit message: Reland "[regexp] Hard-crash on invalid offsets in AdvanceCurrentPosition" This is a reland of 164cf80bbb0a6e091300bfc4cbbe70a6e6bd3e49 The reland fixes UB (left-shift of negative integer type) with a static_cast<uint32_t>. Original change's description: > [regexp] Hard-crash on invalid offsets in AdvanceCurrentPosition > > Drive-by: Range checks in `Emit(byte, twenty_four_bits)` to ensure the > given packed bits actually fit into 24 bits. > > Bug: chromium:1166138 > Change-Id: I2e711e6466bb48d7b9897f68dfe621d12bd92508 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2625877 > Commit-Queue: Jakob Gruber <jgruber@chromium.org> > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Auto-Submit: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/master@{#72064} (cherry picked from commit ff8d0f92d423774cf773b5b4fb48b6744971e27a) No-Try: true No-Presubmit: true No-Tree-Checks: true Tbr: leszeks@chromium.org Bug: chromium:1166138 Change-Id: I514495e14bb99dfc9588fdb4a9f35d67d8d64acb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2626663 Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#72088} Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2742954 Reviewed-by: Jana Grill <janagrill@chromium.org> Commit-Queue: Victor-Gabriel Savu <vsavu@google.com> Cr-Commit-Position: refs/branch-heads/8.6@{nodejs#64} Cr-Branched-From: a64aed2333abf49e494d2a5ce24bbd14fff19f60-refs/heads/8.6.395@{#1} Cr-Branched-From: a626bc036236c9bf92ac7b87dc40c9e538b087e3-refs/heads/master@{#69472} Refs: v8/v8@53c4d05
targos
added a commit
that referenced
this issue
Apr 30, 2021
Original commit message: Reland "[regexp] Hard-crash on invalid offsets in AdvanceCurrentPosition" This is a reland of 164cf80bbb0a6e091300bfc4cbbe70a6e6bd3e49 The reland fixes UB (left-shift of negative integer type) with a static_cast<uint32_t>. Original change's description: > [regexp] Hard-crash on invalid offsets in AdvanceCurrentPosition > > Drive-by: Range checks in `Emit(byte, twenty_four_bits)` to ensure the > given packed bits actually fit into 24 bits. > > Bug: chromium:1166138 > Change-Id: I2e711e6466bb48d7b9897f68dfe621d12bd92508 > Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2625877 > Commit-Queue: Jakob Gruber <jgruber@chromium.org> > Commit-Queue: Leszek Swirski <leszeks@chromium.org> > Auto-Submit: Jakob Gruber <jgruber@chromium.org> > Reviewed-by: Leszek Swirski <leszeks@chromium.org> > Cr-Commit-Position: refs/heads/master@{#72064} (cherry picked from commit ff8d0f92d423774cf773b5b4fb48b6744971e27a) No-Try: true No-Presubmit: true No-Tree-Checks: true Tbr: leszeks@chromium.org Bug: chromium:1166138 Change-Id: I514495e14bb99dfc9588fdb4a9f35d67d8d64acb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2626663 Reviewed-by: Jakob Gruber <jgruber@chromium.org> Commit-Queue: Jakob Gruber <jgruber@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#72088} Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2742954 Reviewed-by: Jana Grill <janagrill@chromium.org> Commit-Queue: Victor-Gabriel Savu <vsavu@google.com> Cr-Commit-Position: refs/branch-heads/8.6@{#64} Cr-Branched-From: a64aed2333abf49e494d2a5ce24bbd14fff19f60-refs/heads/8.6.395@{#1} Cr-Branched-From: a626bc036236c9bf92ac7b87dc40c9e538b087e3-refs/heads/master@{#69472} Refs: v8/v8@53c4d05 PR-URL: #38275 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Shelley Vohr <codebytere@gmail.com>
This was referenced Jul 17, 2021
This was referenced Sep 13, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
nodejs/node-v0.x-archive#6694
/cc @chrisdickinson
The text was updated successfully, but these errors were encountered: