René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"setkeepalive \u003c 1000 silently ignored","articleBody":"### Version\n\n22.14.0\n\n### Platform\n\n```text\nN/A\n```\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nCreate a TCP socket and call `socket.setKeepAlive(true, 400)`.\n\n### How often does it reproduce? Is there a required condition?\n\nAny keepalive less than 1 second.\n\n### What is the expected behavior? Why is that the expected behavior?\n\nThis should send keepalive packets every 400 ms.\n\nThe documentation says as much:\n\u003e `keepAliveInitialDelay` {number} If set to a positive number, it sets the\n  initial delay before the first keepalive probe is sent on an idle socket.\n  **Default:** `0`.\n\n### What do you see instead?\n\nThe code truncates to the nearest 1000ms, so the socket doesn't send keepalive packets and no error is issued.\n\n\n### Additional information\n\nIt seems this parameter is even broken in the tests.\n\nhttps://github.com/nodejs/node/blob/3db54912fa2e4a696d4e2ec27dfb2aeecfc65191/test/parallel/test-net-keepalive.js#L42\nhttps://github.com/nodejs/node/blob/3db54912fa2e4a696d4e2ec27dfb2aeecfc65191/test/parallel/test-net-persistent-keepalive.js#L30\n\nIdeally, the keepalive interval would be respected in milliseconds. Assuming that's infeasible,\n1. a runtime warning should be issued if setKeepAlive is given a value \u003c1000.\n2. the documentation should be updated to reflect that, even though the value is given in milliseconds, it will only be respected to the second.","author":{"url":"https://github.com/rotu","@type":"Person","name":"rotu"},"datePublished":"2025-04-01T17:13:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/57712/node/issues/57712"}