Real Windows 10 hardware turned up two failures the macOS and cross-compile checks could not see: - squid-core::fs reported every file's logical length as its allocated size, because `allocated_bytes` returned 0 on non-Unix and `on_disk()` then fell back to logical. NTFS only answers the allocation question through a handle, so ask `GetFileInformationByHandleEx(FileStandardInfo)` for files big enough to distort a total. Files below the cutoff keep counting as their length, which is also what keeps MFT-resident entries — they report an allocation of 0 — from shrinking a cache cleanup down to nothing. - the "a plain user can still uninstall into /Applications" safety test hard coded a Unix path, so on Windows it asserted that a folder the policy never looked at was refused. The fixture now comes from the policy's own shared install folder, `/Applications` on Unix and the machine-wide program-data folders on Windows. Also added: - `a_written_file_reports_what_the_volume_gave_it`, the cross-platform invariant the missing backend silently violated. - the sparse-file test now marks its file sparse via `fsutil` on Windows and skips when the volume will not cooperate, instead of pretending a hole exists. - `scripts/win-sync.sh`, `scripts/win-check.ps1` and `scripts/win-hwcheck.ps1` for iterating against a LAN Windows host over SSH without git credentials. |
||
|---|---|---|
| .. | ||
| ci-windows.ps1 | ||
| install.sh | ||
| release.sh | ||
| tui_smoke.py | ||
| win-check.ps1 | ||
| win-hwcheck.ps1 | ||
| win-sync.sh | ||