-
Notifications
You must be signed in to change notification settings - Fork 566
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix: post request signal #3354
fix: post request signal #3354
Conversation
@@ -36,9 +36,11 @@ test('post abort signal', async (t) => { | |||
|
|||
server.listen(0, async () => { | |||
const ac = new AbortController() | |||
const ures = await request(`http://0.0.0.0:${server.address().port}`, { signal: ac.signal }) | |||
const uresPromise = request(`http://0.0.0.0:${server.address().port}`, { signal: ac.signal }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ℹ️ this test was wrong because request
api terminates when the stream has been completely consumed, so the connection has been closed. If we postpone the await
we can throw the abort before dispatch starts consuming the stream, so the request is actually aborted
const ures = await request(`http://0.0.0.0:${server.address().port}`, { signal: ac.signal }) | ||
ac.abort() | ||
t.equal(await ures.body.text(), 'asd') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ℹ️ in this case the abort signal is ignored since the request is completed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since these are modeled after the fetch body mixins, I'm wondering if they should throw. In the fetch spec, if a request was aborted and you attempt to read the body, it'll throw an error. @ronag wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes kind of sense
RSLGTM
* upstream/main: fix: use explicit flag for when use has interacted with stream (nodejs#3361) refactor: simplify signal handling (nodejs#3362) fix: consider bytes read when dumping (nodejs#3360) websocket: don't use pooled buffer in mask pool (nodejs#3357) Revert "fix: post request signal (nodejs#3354)" (nodejs#3359) fix: post request signal (nodejs#3354) build(deps): bump node from `075a5cc` to `9af472b` in /build (nodejs#3355)
Hey, how can I add this fix to my nodejs? (I'm running latest and it's not there iiuc) |
Fix post request abort signal
Fix issue #3353
Rationale
Request API doesn't remove the signal listener after complete the request
Changes
Remove abort listener after success
Status