| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Hmm.. I'm thinking this is more bug fix than breaking change. What do you think @mcollina? |
Sorry, something went wrong.
There was a problem hiding this comment.
This will need a unit test.
I'm happy to land this as a bug fix as long as it does not break anything on CITGM.
Sorry, something went wrong.
|
def bugfix |
Sorry, something went wrong.
Sorry, something went wrong.
|
test added and fixed |
Sorry, something went wrong.
There was a problem hiding this comment.
I would still consider this a bugfix, but we should:
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
@mcollina: Sorry, found further issues. Consider the updated tests. We now will throw ERR_STREAM_DESTROYED on some tests that assume ERR_STREAM_WRITE_AFTER_END also we now send the err on the write callback and don't emit it as an error on the stream. How should this be? |
Sorry, something went wrong.
There was a problem hiding this comment.
I wouldn’t mind being careful and labelling this semver-major.
Sorry, something went wrong.
|
Ok, I think everything (expect @mcollina's comment on !err && chinksWritten++) is fixed in a sensical manner. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
It doesn't make much sense (and is a bit weird) to flush a stream which has been destroyed.
I need help creating a relevant test for this.
Checklist
NOTE TO SELF: Look into needFinish & stream destroyed. errorOrDestroy added in this PR should preferably be async.