to avoid crash because of null pointer

[jackzhp]

null might be expected along the call stack, but here, null is not expected, so just return, and crash could be avoided.

when it crashes, req_wrap is null. For more information, please refer to #59465

[aduh95]

Any chance you could add a test case that fails without this patch and passes with it?

[jackzhp]

Any chance you could add a test case that fails without this patch and passes with it?

Yes. I just post a comment for #60628. (client.ts & server.ts, with them you will see the client crashes the server very often). Please use them in any way as you wish. I don't know where to put these test files into this project.

By the way, #60628 was to merge it into v24.11.1, while this PR(#60629) was to merge it into main branch.

[aduh95]

By the way, #60628 was to merge it into v24.11.1, while this PR(#60629) was to merge it into main branch.

This first need to be merged to main, backported to v25.x and be released there for at least two weeks before it can land on v24.x. If every one was opening a PR for each release branch they wanted their changes to land, the repo would become unmanageable.

I don't know where to put these test files into this project.

You can have a look at doc/contributing/writing-tests.md for how to do it, the TL;DR is it should ideally be a single JS file inside test/parallel that exits with non-zero code with current main and with code 0 with your patch.