You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
test/parallel/test-zlib-zip-interop.js fails if system's zipinfo is built without natspec #66975
Stock Info-ZIP zipinfo replaces non-ASCII bytes with ? in fnfilter() unless patched with wide-character/UTF-8 printing support (such as USE_NATSPEC or alt-iconv-utf8-print). While unzip -v reports UNICODE_SUPPORT, stock builds still sanitize non-ASCII bytes to ?, so zipinfo outputs unicode-??.txt (or unicode-??????.txt) instead of unicode-名前.txt, failing the assertion.
Proposed fix
When inspecting zipinfo output, if a non-ASCII entry is not found verbatim, check whether zipinfo listed the entry with ? replacement placeholders. (Full UTF-8 extraction and file integrity are already verified by the bsdtar step).
I have a patch prepared with lint and tests verified. Working on a PR.
Activity
ravi-arnan commentedon Oct 24, 2026
I can reproduce this on Linux (NixOS).
Cause
Stock Info-ZIP
zipinforeplaces non-ASCII bytes with?infnfilter()unless patched with wide-character/UTF-8 printing support (such asUSE_NATSPECoralt-iconv-utf8-print). Whileunzip -vreportsUNICODE_SUPPORT, stock builds still sanitize non-ASCII bytes to?, sozipinfooutputsunicode-??.txt(orunicode-??????.txt) instead ofunicode-名前.txt, failing the assertion.Proposed fix
When inspecting
zipinfooutput, if a non-ASCII entry is not found verbatim, check whetherzipinfolisted the entry with?replacement placeholders. (Full UTF-8 extraction and file integrity are already verified by thebsdtarstep).I have a patch prepared with lint and tests verified. Working on a PR.
test: fix zipinfo non-ascii check in test-zlib-zip-interop