nodejs / nodejs/node-core-utils
CLI returns false positive
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 313
- Forks
- 137
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 24
Description
I ran git node land 48349 which showed that This PR should be ready to land, but commit-queue message failed: https://github.com/nodejs/node/pull/48349#issuecomment-1591955940
git node land 48349
✔ Done loading data for nodejs/node/pull/48349
----------------------------------- PR info ------------------------------------
Title src: introduce V8 fast api to `guessHandleType` (#48349)
Author Yagiz Nizipli <yagiz@nizipli.com> (@anonrig)
Branch anonrig:improve-guessHandleType -> nodejs:main
Labels lib / src, performance, needs-ci, commit-queue-failed, commit-queue-rebase
Commits 2
- src: return uint32 for `guessHandleType`
- src: add V8 fast api to `guessHandleType`
Committers 1
- Yagiz Nizipli <yagiz@nizipli.com>
------------------------------ Generated metadata ------------------------------
PR-URL: https://github.com/nodejs/node/pull/48349
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Robert Nagy <ronagy@icloud.com>
Reviewed-By: Minwoo Jung <nodecorelab@gmail.com>
--------------------------------------------------------------------------------
ℹ This PR was created on Mon, 05 Jun 2023 16:41:28 GMT
✔ Approvals: 3
✔ - Matteo Collina (@mcollina) (TSC): https://github.com/nodejs/node/pull/48349#pullrequestreview-1465345051
✔ - Robert Nagy (@ronag) (TSC): https://github.com/nodejs/node/pull/48349#pullrequestreview-1465728186
✔ - Minwoo Jung (@JungMinu): https://github.com/nodejs/node/pull/48349#pullrequestreview-1471073777
✔ Last GitHub CI successful
ℹ Last Full PR CI on 2023-06-14T20:45:52Z: https://ci.nodejs.org/job/node-test-pull-request/52248/
⠋ Querying data for job/node-test-pull-request/52248/ ✔ Last Jenkins CI successful
--------------------------------------------------------------------------------
? This PR should be ready to land, do you want to continue? (Y/n)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing git node land 48349 and compare the reported readiness with the linked commit-queue failure message. Trace the CLI land command's readiness and commit-queue status handling; done means a failed commit-queue result is not reported as ready to land.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100