| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
Codecov ReportAttention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
@@ Coverage Diff @@
## main #57644 +/- ##
==========================================
- Coverage 90.22% 90.22% -0.01%
==========================================
Files 630 630
Lines 185055 185055
Branches 36216 36212 -4
==========================================
- Hits 166975 166965 -10
- Misses 11042 11050 +8
- Partials 7038 7040 +2
... and 22 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
|
@RafaelGSS hi RafaelGSS, I have reviewed all your test files in 1b693fa, and it seems that none of them cover the Http2Session::OnFrameNotSent function test. I attempted to write a test for it, but it is quite difficult to trigger Http2Session::OnFrameNotSent with frame->hd.type equal to 0x07. Do you have any good ideas on how to achieve this? Alternatively, is it possible to merge this patch first if you think this modification is urgent. |
Sorry, something went wrong.
|
@hgqxjj, it seems your change is breaking test-http2-premature-close. This test is historically known for being flaky, so I'll re-run the suite just to make sure. |
Sorry, something went wrong.
|
@RafaelGSS I think my change is unlikely to touch test-http2-premature-close. Maybe it still be flaky, haha |
Sorry, something went wrong.
|
@RafaelGSS Unfortunately, the test failed again due to a timeout. I conducted the same test using different versions of Node.js in my side. When running test-http2-premature-close.js with Node.js 14.19, the program terminates as expected. However, when testing with Node.js 20.12, the program gets stuck. Based on my analysis of the test-http2-premature-close.js script combined with debug logs, there are two errors in the client's header frame content. In Node.js 14.19, these errors cause the server to send an RST_STREAM upon receiving the header frame. For some reason, this also triggers the onFrameError function, leading to the session being closed, which subsequently triggers server.close(), allowing the program to terminate. However, in Node.js 20.12, server seems to have ignored these errors and did not send RST_STREAM , and onFrameError is not triggered, and server.close() is not called, causing the program to hang. Therefore, the test failure does not seem to be related to my modifications but rather an issue with test-http2-premature-close.js itself. |
Sorry, something went wrong.
|
@RafaelGSS hi RafaelGSS,i already correct header frame content according to http2 related protocol so that make it exited successfully,please re-running the test suite to make sure at your convenience . |
Sorry, something went wrong.
According to the description above, this should be checking whether frame->hd.type is NGHTTP2_GOAWAY, and the value of NGHTTP2_GOAWAY is 0x07. However, it is written as 0x03 here, which I think it is an error.
previously, due to some error in the content of the header frame, the script could not exit properly, which eventually led to a timeout error,this commit correct header frame content according to http2 related protocol so that make it exited successfully.
correct comments
|
hi @RafaelGSS ,currently, all tests have passed. Could you please take some time to review this patch ? Thanks in advance |
Sorry, something went wrong.
Failed to start CI⚠ No approving reviews found ✘ Refusing to run CI on potentially unsafe PRhttps://github.com/nodejs/node/actions/runs/14248886630 |
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm, but this should wait @RafaelGSS approval too.
Sorry, something went wrong.
Sorry, something went wrong.
|
I will review this PR carefully tomorrow. I'll double check the memory leak. |
Sorry, something went wrong.
|
hi @RafaelGSS , I'll paste some screenshots below to help explain the changes I made. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
http2: fix a typo in the check for frame->hd.type in 1b693fa
According to the description above, this should be checking
whether frame->hd.type is NGHTTP2_GOAWAY,
and the value of NGHTTP2_GOAWAY is 0x07. However,
it is written as 0x03 here, which I think it is a typo.
Refs: 1b693fa