New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Error Unexpected when you try to run build after first time on windows network shared folder #19785
Labels
Milestone
Comments
Yabgu
added
the
bug
Observed behavior contradicts documented or intended behavior
label
Apr 28, 2024
How about zig 0.12? |
It happens with 0.12 as well. |
Can reproduce. Stacktrace with a debug build of Zig (
|
squeek502
added a commit
to squeek502/zig
that referenced
this issue
Apr 29, 2024
Before this commit, the DIRECTORY_NOT_EMPTY/FILE_IS_A_DIRECTORY/NOT_A_DIRECTORY statuses were assumed only to be possible when using `FILE_RENAME_INFORMATION_EX` and `FILE_RENAME_POSIX_SEMANTICS`, but that has empirically been shown to be false; a networked samba share can return the DIRECTORY_NOT_EMPTY status from `FILE_RENAME_INFORMATION` (which doesn't support `FILE_RENAME_POSIX_SEMANTICS`). `FILE_IS_A_DIRECTORY` and `NOT_A_DIRECTORY` were not proven to be possible, but they were also moved to the outer switch just in case. Fixes ziglang#19785
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Zig Version
0.11.0
Steps to Reproduce and Observed Behavior
Create hello world project in samba network shared folder (mounted as drive Z:\ in my case) with zig init-exe and then run zig build twice.
Expected Behavior
It should rebuild
The text was updated successfully, but these errors were encountered: