-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
deps: update nghttp3 to 1.0.0 #47576
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
Commit Queue failed- Loading data for nodejs/node/pull/47576 ✔ Done loading data for nodejs/node/pull/47576 ----------------------------------- PR info ------------------------------------ Title deps: update nghttp3 to 0.10.0 (#47576) ⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile! Branch nodejs-github-bot:actions/tools-update-nghttp3 -> nodejs:main Labels needs-ci, quic, dependencies, dont-land-on-v14.x Commits 1 - deps: update nghttp3 to 0.10.0 Committers 1 - Node.js GitHub Bot PR-URL: https://github.com/nodejs/node/pull/47576 Reviewed-By: Luigi Pinca Reviewed-By: Mohammed Keyvanzadeh Reviewed-By: Tobias Nießen Reviewed-By: Marco Ippolito Reviewed-By: James M Snell ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/47576 Reviewed-By: Luigi Pinca Reviewed-By: Mohammed Keyvanzadeh Reviewed-By: Tobias Nießen Reviewed-By: Marco Ippolito Reviewed-By: James M Snell -------------------------------------------------------------------------------- ℹ This PR was created on Sun, 16 Apr 2023 00:24:33 GMT ✔ Approvals: 5 ✔ - Luigi Pinca (@lpinca): https://github.com/nodejs/node/pull/47576#pullrequestreview-1386703737 ✔ - Mohammed Keyvanzadeh (@VoltrexKeyva): https://github.com/nodejs/node/pull/47576#pullrequestreview-1386816166 ✔ - Tobias Nießen (@tniessen) (TSC): https://github.com/nodejs/node/pull/47576#pullrequestreview-1387101562 ✔ - Marco Ippolito (@marco-ippolito): https://github.com/nodejs/node/pull/47576#pullrequestreview-1387635921 ✔ - James M Snell (@jasnell) (TSC): https://github.com/nodejs/node/pull/47576#pullrequestreview-1389053297 ✔ Last GitHub CI successful ✘ No Jenkins CI runs detected -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncuhttps://github.com/nodejs/node/actions/runs/4805669128 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just making sure this doesn't land as-is
That's really strange. I can't explain why, cause locally never happens, but the job on 30th April that try to update
node/deps/ngtcp2/nghttp3/lib/includes/nghttp3/nghttp3.h Lines 2580 to 2596 in 69f8b22
node/deps/ngtcp2/ngtcp2/lib/ngtcp2_cc.c Lines 364 to 382 in 5e7d37e
Of course both duplicate codes never existed in the depencies repos Last but not least the job that in theory should have skipped the update, because locally it actually skips the update, fix these differences with a second commit for the same version (on 7th May) |
PR-URL: nodejs#47992 Refs: nodejs#47576 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com> Reviewed-By: Deokjin Kim <deokjin81.kim@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
@marco-ippolito wondering if you are still looking at this issue? I wonder if it might be at all related to the same branch being used by the updater each time. Have we tried closing this PR, deleting the branch and seeing if the problem re-occurs in the newly created PR? |
I totally missed this notification, I agree we should delete it and see what happens with the update. I had look at the code and tested on my machine and it was all working fine |
Closing and will delete branch, then we can see what happens |
Branch deleted |
This is an automated update of nghttp3 to 1.0.0.