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
FileCache uses : in cache paths, creating NTFS alternate data streams on Windows #255
wasm_pkg_client::FileCache derives cache paths directly from values containing ::
Blobs use digest.to_string(), producing paths such as sha256:<hex>.
Releases use <package>-<version>.json, while PackageRef displays as <namespace>:<name>.
On NTFS, the colon does not create an ordinary filename. It creates an alternate data stream:
sha256:<hex> becomes stream <hex> on a base file named sha256.
wasi:http-0.2.0.json becomes stream http-0.2.0.json on a base file named wasi.
The paths remain directly readable when their full names are known, which can hide the problem. However, normal directory enumeration only returns the base files and does not return the logical cache entries.
Impact
read_dir cannot enumerate blob or release entries on Windows.
Orphaned or truncated blobs cannot be discovered and removed through portable filesystem APIs.
Blob writes should also use a temporary file followed by an atomic rename so interrupted downloads never leave a partial entry at the final digest path.
Because this is a cache, migration could be handled by using a new layout directory and treating older entries as cache misses. A temporary legacy lookup path could be retained if preserving existing caches is important.
Activity