| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Review requested:
|
Sorry, something went wrong.
Correcting the nodejs#50194 backporting mistake. closeIdleConnections shouldnot be called while server.close in node v18. This behavior is for node v19 and above. fixes: nodejs#52330, nodejs#51677
|
the timeout tests should not be deleted, as they check the interval change which is still kept. |
Sorry, something went wrong.
|
Correct. I doubted that too. I misunderstood the previous message regarding deleting test. @Linkgoron |
Sorry, something went wrong.
|
@Linkgoron should i be raising the PR against v18.x or v18.x-staging branch? CC: @richardlau |
Sorry, something went wrong.
v18.x-staging. |
Sorry, something went wrong.
|
Done |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
can we go ahead with review and merge? |
Sorry, something went wrong.
|
can we target this for v18.20.3 release? |
Sorry, something went wrong.
|
Will there be separate PR for v19/20/21 ? or does this propagate to newer versions? |
Sorry, something went wrong.
No. This new behavior is expected in v19 and above. https://nodejs.org/docs/latest-v19.x/api/http.html#serverclosecallback This PR is only for v18 where this is not expected and was a backporting mistake. https://nodejs.org/docs/latest-v18.x/api/http.html#serverclosecallback |
Sorry, something went wrong.
|
@richardlau can we get this merge and land on v18? |
Sorry, something went wrong.
Four quick-adds the S1 review flagged for S2 to bring along: - close(): explicit closeIdleConnections()/closeAllConnections() fallback, typeof-guarded for Node 18.0-18.18 (the methods land in 18.2.0, nodejs/node#42812) — Node's own close() briefly auto-invoked closeIdleConnections internally on some 18.x releases via a mistaken v19-only backport, reverted in 18.20.3 (nodejs/node#52336), so close() alone can't be assumed sufficient on any given patch. - Extend the ENOENT watch-setup comment: a pages/or assets/ directory created after startup is never picked up until pptfast serve restarts. - Two watch tests: a file appearing in assets/ triggers a rebuild, and a deck.spec.json-only edit (no pages/ touch) triggers one too — S1's own coverage only exercised pages/*.json. - One-line comment at runPreview's moved mkdir(outDir) noting the deliberate after-render timing.
| Back | FazBrowse Home | New Git URL |
Correcting the #50194 backporting mistake.
closeIdleConnections shouldnot be called while server.close in node v18. This behavior is for node v19 and above.
fixes: #52330, #51677