| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@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.
|
@mcollina does this supersede my zlib destroy leak PR? |
Sorry, something went wrong.
|
Nit: destroy(err) |
Sorry, something went wrong.
|
@mafintosh which one? Very likely that should be merged first. |
Sorry, something went wrong.
There was a problem hiding this comment.
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 a problem hiding this comment.
any reason for rejects rather than reject?
Sorry, something went wrong.
There was a problem hiding this comment.
none, I’ll fix it.
Sorry, something went wrong.
|
@devsnek this is normalizing a race condition that we cannot get rid of inside our stream machinery :/. |
Sorry, something went wrong.
Sorry, something went wrong.
|
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 a problem hiding this comment.
Can you add a comment here describing what this condition means?
Sorry, something went wrong.
There was a problem hiding this comment.
This changes timing for the close callback… is that intentional?
Sorry, something went wrong.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/18090/ PTAL, this should be ready for review. |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
could use stream.finished to simplify in the future, but 👍
Sorry, something went wrong.
There was a problem hiding this comment.
| assert.strictEqual(err, e); | |
| assert.strictEqual(e, err); |
Sorry, something went wrong.
There was a problem hiding this comment.
| assert.strictEqual(err, e); | |
| assert.strictEqual(e, err); |
Sorry, something went wrong.
|
@mcollina There’s nothing speaking against landing this as far as I am concerned :) |
Sorry, something went wrong.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/18110/ PTAL, I've switched to use finished instead. |
Sorry, something went wrong.
|
Still LGTM. |
Sorry, something went wrong.
|
(Also still LGTM for the record) |
Sorry, something went wrong.
Sorry, something went wrong.
|
go for it!
Il giorno lun 26 nov 2018 alle 22:41 Myles Borins <notifications@github.com>
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.
| Back | FazBrowse Home | New Git URL |
This PR is twofold:
Fixes #23730 .
Checklist