René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"zlib: Zstd decompression silently accepts truncated input","articleBody":"### Version\n\nlatest main branch\n\n### Platform\n\n```text\n7.1.3-arch1-3\n```\n\n### Subsystem\n\nzlib\n\n### What steps will reproduce the bug?\n\n```js\n  const assert = require('node:assert');\n  const zlib = require('node:zlib');\n\n  const compressed = zlib.zstdCompressSync('hello world');\n  const truncated = compressed.subarray(0, compressed.length / 2);\n\n  const actual = zlib.zstdDecompressSync(truncated);\n  console.log(actual.toString()); // \"h\"\n```\n\n\n\n### How often does it reproduce? Is there a required condition?\n\nEvery time\n\n### What is the expected behavior? Why is that the expected behavior?\n\nWith the default finishFlush: ZSTD_e_end, both APIs should report an unexpected end of file error when the Zstd frame is incomplete.While other decompress api in zlib module would throw \"unexpeted of EOF\" for imcomplete input so I just assume this is a kind of implementation problem.\n\n### What do you see instead?\n\n`zstdDecompress()` and `zstdDecompressSync()` currently succeed when the  input ends before a complete Zstd frame has been received.\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/Archkon","@type":"Person","name":"Archkon"},"datePublished":"2026-07-19T04:39:28.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/64592/node/issues/64592"}