Conversation
nodejs-github-bot
added
cluster
|
Welcome to Node.js, and thank you for your first contribution! Before review, please take a moment to read:
Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal. Caution AgentScan found account activity patterns that may be consistent with automation. This is a heuristic, not proof that this pull request was opened by an agent or violates policy. AI-assisted contributions are permitted, but automated tooling must not open pull requests without advance approval, and contributors must personally understand, test, verify, and take responsibility for every submitted change. See the AgentScan analysis, AI use policy, and automation policy for additional context. |
`worker.isConnected()` and `worker.isDead()` described their boolean result only in prose, so the documentation tooling had no return type for them. Signed-off-by: Daniel Pinto <1619617+Cayan@users.noreply.github.com> Assisted-by: a frontier reasoning model
4bcb458 to
214e3dc
Compare
Renegade334
added
author ready
4 participants
worker.isConnected()andworker.isDead()describe their boolean result only in prose, so the doc tooling has no return type for them. This adds* Returns: {boolean}to both, the same way #65307 did forfs.md.Both return
this.process.connectedand an exit/signal check (lib/internal/cluster/worker.js). I checked on v24 that they returntrue/falsewhile the worker runs andfalse/trueafter it exits.Written with AI assistance (see the
Assisted-bytrailer); I reviewed the change and ran the check above myself.