stream: end(callback) does not propagate write after end to callback
Open
Nobody has claimed this yet.
confirmed-bug
http
stream
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
w.end();
w.end('asd', (err) => {
assert.strictEqual(err.code, 'ERR_STREAM_WRITE_AFTER_END'); // Fails
});
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the provided w.end() example and trace the stream end callback handling. Done means the callback receives an error with code ERR_STREAM_WRITE_AFTER_END, backed by a regression test for the shown sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100