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 — test: reach res._dump after abort ClientRequest by tadhgcreedon · Pull Request #24191 · nodejs/node Conversation
|
|
@tadhgcreedon I’m not sure, but would it maybe make sense to test both cases here, e.g. by creating a new test file rather than modifying an existing one? I think this might be affecting the previous functionality of the test… (/cc @nodejs/http) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Yeah, a separate new test file may be better |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Sure, makes sense. Will create a new test file then update. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
3179181 to
1a544be
Compare
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Hi @tadhgcreedon, the author of the commits in this PR is not registered on GitHub (steps defined here) Either:
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
1a544be to
c37a91d
Compare
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Resume: https://ci.nodejs.org/job/node-test-commit-windows-fanned/22295/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
@addaleax LGTY? |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
|
||
| req.end(); | ||
| req.abort(); | ||
| req.abort(); |
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Havn't checked this completely, but two req.aborts are intentional?
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.
/ping @tadhgcreedon Two abort() calls like that are intentional? If so, great. If not, can you remove one? Or I can totally remove one. Either way. I just want to see this get merged....
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.
|
Resume Build CI: https://ci.nodejs.org/job/node-test-pull-request/19013/ |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: nodejs#24191 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Rich Trott <[email protected]>
|
Landed in f5b8853. Thanks for the contribution! 🎉 (If you're interested in other possible contributions to Node.js but don't have a good idea of where to start looking, some ideas are posted at https://www.nodetodo.org/next-steps/.) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
PR-URL: #24191 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Rich Trott <[email protected]>
PR-URL: nodejs#24191 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Rich Trott <[email protected]>
PR-URL: #24191 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Rich Trott <[email protected]>
PR-URL: #24191 Reviewed-By: Ouyang Yadong <[email protected]> Reviewed-By: Rich Trott <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.