René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Buffer.byteLength benchmark does not test base64 encoding correctly","articleBody":"### Version\n\nOutput of node -v: (e.g. v20.10.0)\n\n### Platform\n\n```text\nOutput of uname -a (for UNIX) or Windows version string (for Windows).\n```\n\n### Subsystem\n\nbuffers (benchmark/buffers/buffer-bytelength-string.js)\n\n### What steps will reproduce the bug?\n\nRun the buffer byteLength benchmark for base64 encoding.\nExpected: getInput should return a base64-encoded string when encoding is 'base64'.\nActual: getInput returns the original string, not the base64-encoded string.\n\n### How often does it reproduce? Is there a required condition?\n\nRun the buffer byteLength benchmark for base64 encoding.\nExpected: getInput should return a base64-encoded string when encoding is 'base64'.\nActual: getInput returns the original string, not the base64-encoded string.\n\n### What is the expected behavior? Why is that the expected behavior?\n\ngetInput should return the base64-encoded string so the benchmark accurately tests Buffer.byteLength for base64 input.\n\n\n\n### What do you see instead?\n\nThe benchmark tests the original string, not the base64-encoded string.\n\n### Additional information\n\nSuggested fix:\nIn benchmark/buffers/buffer-bytelength-string.js, update getInput to return Buffer.from(original, 'utf8').toString('base64') when encoding is 'base64'.\nThis will ensure the benchmark is correct.","author":{"url":"https://github.com/kisugez","@type":"Person","name":"kisugez"},"datePublished":"2025-11-24T10:32:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/60836/node/issues/60836"}