| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Whether a symlink can be created isn't decided by the platform alone: on Windows it needs Developer Mode or SeCreateSymbolicLinkPrivilege.
These called os.symlink unguarded, so on a Windows account without the privilege they errored with WinError 1314 instead of being skipped.
test_index had a private probe and test_refs repeated the same check inline.
| Back | FazBrowse Home | New Git URL |
Summary
The tests that were erroring:
CI doesn't show this because the GitHub Windows runners hold the privilege, so the three run and pass there.
One behaviour note: the probe used to return early on non-Windows, so it never created anything. Now it always creates and removes a symlink in a temporary directory, on every platform.
Validation
Windows 11, Python 3.13, after ./init-tests-after-clone.sh: