GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||
GeezerVison is showing github.com — Ensure async iteration works with destroyed streams by mcollina · Pull Request #23785 · nodejs/node Conversation
|
|
@mcollina build started: https://ci.nodejs.org/blue/organizations/jenkins/node-test-pull-request-lite-pipeline/detail/node-test-pull-request-lite-pipeline/1317/pipeline |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
@mcollina does this supersede my zlib destroy leak PR? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Nit: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@mafintosh which one? Very likely that should be merged first. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It seems this relies on a race condition? I won't pretend to know anything about our crazy streams but I want to just verify what's going on here is what is intended.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
any reason for rejects rather than reject?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
none, I’ll fix it.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@devsnek this is normalizing a race condition that we cannot get rid of inside our stream machinery :/. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Ah I didn’t know we were working on essentially the same issue! Can you pick up the change that I did inside processCallback? It might even be worth a test on its own. I’ll rebase this on top of yours. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Can you add a comment here describing what this condition means?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
This changes timing for the close callback… is that intentional?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/18090/ PTAL, this should be ready for review. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
could use stream.finished to simplify in the future, but 👍
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
| assert.strictEqual(err, e); | |
| assert.strictEqual(e, err); |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
| assert.strictEqual(err, e); | |
| assert.strictEqual(e, err); |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@mcollina There’s nothing speaking against landing this as far as I am concerned :) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/18110/ PTAL, I've switched to use |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Still LGTM. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Landed in 3ec8cec |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Fixes #23730. PR-URL: #23785 Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matheus Marchini <[email protected]>
|
(Also still LGTM for the record) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Fixes #23730. PR-URL: #23785 Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matheus Marchini <[email protected]>
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
go for it!
Il giorno lun 26 nov 2018 alle 22:41 Myles Borins <[email protected]>
ha scritto:
… Landed in 10.x with 398418d
<398418d>
and b1e1fe4
<b1e1fe4>
Please lmk if it should be backed out
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#23785 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADL4-2fOTTylhaBVvajyK70fXegKpuvks5uzGAUgaJpZM4Xx6oH>
.
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Fixes #23730. PR-URL: #23785 Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matheus Marchini <[email protected]>
Fixes #23730. PR-URL: #23785 Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matheus Marchini <[email protected]>
Fixes #23730. PR-URL: #23785 Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matheus Marchini <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
Stream destruction breaks async-iteration and ends nodejs event loop
There was an error while loading. Please reload this page.