-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI failure with v18.19.0 #5198
Comments
The commit that triggers our CI failure is nodejs/node@2969722. |
So closeIdleConnections was backported? |
Looks that way. |
There was discussion at the end of nodejs/node#48383 about it breaking core's CITGM within Fastify. |
4 tasks
Reopened #5195 |
My bad, I didn't notice this was actually backported to node v18, the last few months have been hectic. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#5195 shows that our CI fails with Node.js v18.19.0. I can confirm this locally. I am seeing issues with v18.19.0 in another project and found the commit breaking that project to be nodejs/node@bac9b17. However, a build of Node with that commit passes the Fastify CI. So our issue here is somewhere between that commit and the
v18.19.0
tag.The text was updated successfully, but these errors were encountered: