ziglang/zig
261
5.9k
Fork
You've already forked zig
763

Calling createFileAtomic throws unexpected errno: 95 #31231

Closed
opened 2026年02月16日 07:53:31 +01:00 by freakman · 13 comments

Zig Version

0.16.0-dev.2611+f996d2866

Steps to Reproduce and Observed Behavior

On Linux Mint, this snippet throws unexpected errno 95:

pubfnmain(init:@import("std").process.Init)!void{_=try@import("std").Io.Dir.cwd().createFileAtomic(init.io,"./test.txt",.{});}
 $ zig run src/main.zig 1 ↵
unexpected errno: 95
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/posix.zig:1692:40: 0x106e400 in unexpectedErrno (std.zig)
 std.debug.dumpCurrentStackTrace(.{});
 ^
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:1407:37: 0x106c5e8 in unexpectedErrno (std.zig)
 return posix.unexpectedErrno(err);
 ^
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:4763:61: 0x1045ac5 in dirCreateFileAtomic (std.zig)
 else => |err| return syscall.unexpectedErrno(err),
 ^
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Dir.zig:1815:41: 0x11b1173 in createFileAtomic (std.zig)
 return io.vtable.dirCreateFileAtomic(io.userdata, dir, sub_path, options);
 ^
~/zig/lol/src/main.zig:2:57: 0x11aef56 in main (main.zig)
 _ = try @import("std").Io.Dir.cwd().createFileAtomic(init.io, "./test.txt", .{});
 ^
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/start.zig:716:30: 0x11af94f in callMain (std.zig)
 return wrapMain(root.main(.{
 ^
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/start.zig:190:5: 0x11aee91 in _start (std.zig)
 asm volatile (switch (native_arch) {
 ^
error: Unexpected
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/posix.zig:1694:5: 0x106e405 in unexpectedErrno (std.zig)
 return error.Unexpected;
 ^
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:1407:9: 0x106c5f2 in unexpectedErrno (std.zig)
 return posix.unexpectedErrno(err);
 ^
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:4763:31: 0x1045b06 in dirCreateFileAtomic (std.zig)
 else => |err| return syscall.unexpectedErrno(err),
 ^
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Dir.zig:1815:5: 0x11b11a8 in createFileAtomic (std.zig)
 return io.vtable.dirCreateFileAtomic(io.userdata, dir, sub_path, options);
 ^
~/zig/lol/src/main.zig:2:9: 0x11aef9e in main (main.zig)
 _ = try @import("std").Io.Dir.cwd().createFileAtomic(init.io, "./test.txt", .{});
 ^

Adding .OPPNOTSUP to this prong in lib/std/Io/Threaded.zig fixes the issue (line 4742):

.ISDIR,.NOENT,.OPNOTSUPP=>{// Ambiguous error code. It might mean the file system// does not support O_TMPFILE. Therefore, we must fall// back to not using O_TMPFILE.syscall.finish();break:tmpfile;},

Here's my OS info:

Kernel: 6.8.0-100-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc
Desktop: Cinnamon v: 6.6.7 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 vt: 7 dm: LightDM v: 1.30.0
 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble

Expected Behavior

No error, file created as normal

### Zig Version 0.16.0-dev.2611+f996d2866 ### Steps to Reproduce and Observed Behavior On Linux Mint, this snippet throws unexpected errno 95: ```zig pub fn main(init: @import("std").process.Init) !void { _ = try @import("std").Io.Dir.cwd().createFileAtomic(init.io, "./test.txt", .{}); } ``` ``` $ zig run src/main.zig 1 ↵ unexpected errno: 95 ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/posix.zig:1692:40: 0x106e400 in unexpectedErrno (std.zig) std.debug.dumpCurrentStackTrace(.{}); ^ ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:1407:37: 0x106c5e8 in unexpectedErrno (std.zig) return posix.unexpectedErrno(err); ^ ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:4763:61: 0x1045ac5 in dirCreateFileAtomic (std.zig) else => |err| return syscall.unexpectedErrno(err), ^ ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Dir.zig:1815:41: 0x11b1173 in createFileAtomic (std.zig) return io.vtable.dirCreateFileAtomic(io.userdata, dir, sub_path, options); ^ ~/zig/lol/src/main.zig:2:57: 0x11aef56 in main (main.zig) _ = try @import("std").Io.Dir.cwd().createFileAtomic(init.io, "./test.txt", .{}); ^ ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/start.zig:716:30: 0x11af94f in callMain (std.zig) return wrapMain(root.main(.{ ^ ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/start.zig:190:5: 0x11aee91 in _start (std.zig) asm volatile (switch (native_arch) { ^ error: Unexpected ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/posix.zig:1694:5: 0x106e405 in unexpectedErrno (std.zig) return error.Unexpected; ^ ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:1407:9: 0x106c5f2 in unexpectedErrno (std.zig) return posix.unexpectedErrno(err); ^ ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:4763:31: 0x1045b06 in dirCreateFileAtomic (std.zig) else => |err| return syscall.unexpectedErrno(err), ^ ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Dir.zig:1815:5: 0x11b11a8 in createFileAtomic (std.zig) return io.vtable.dirCreateFileAtomic(io.userdata, dir, sub_path, options); ^ ~/zig/lol/src/main.zig:2:9: 0x11aef9e in main (main.zig) _ = try @import("std").Io.Dir.cwd().createFileAtomic(init.io, "./test.txt", .{}); ^ ``` Adding `.OPPNOTSUP` to this prong in `lib/std/Io/Threaded.zig` fixes the issue (line 4742): ```zig .ISDIR, .NOENT, .OPNOTSUPP => { // Ambiguous error code. It might mean the file system // does not support O_TMPFILE. Therefore, we must fall // back to not using O_TMPFILE. syscall.finish(); break :tmpfile; }, ``` Here's my OS info: ``` Kernel: 6.8.0-100-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.6.7 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble ``` ### Expected Behavior No error, file created as normal
Contributor
Copy link

From open(2):

EOPNOTSUPP
 The filesystem containing path does not support O_TMPFILE.

Note that the fix might not be as simple as just adding that. While we were discussing this and trying out the patch, it caused the following while compiling ZLS:

thread 25384 panic: programmer bug caused syscall error: INVAL
error return context:
~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:4143:31: 0x10fcd9a in dirAccessPosix (std.zig)
 .NOENT => return error.FileNotFound,
From open(2): ``` EOPNOTSUPP The filesystem containing path does not support O_TMPFILE. ``` Note that the fix might not be as simple as just adding that. While we were discussing this and trying out the patch, it caused the following while compiling ZLS: ``` thread 25384 panic: programmer bug caused syscall error: INVAL error return context: ~/zig/0.16.0-dev.2611+f996d2866/files/lib/std/Io/Threaded.zig:4143:31: 0x10fcd9a in dirAccessPosix (std.zig) .NOENT => return error.FileNotFound, ```

@eshom the syscall error seems to be from the b.addOptions(), which uses createFileAtomic and File.Atomic.link
Calling this gives the same error:

pubfnmain(init:std.process.Init)!void{varf=trystd.Io.Dir.cwd().createFileAtomic(init.io,"./test.txt",.{});deferf.deinit(init.io);tryf.link(init.io);}
thread 25817 panic: programmer bug caused syscall error: INVAL
~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Threaded.zig:14360:34: 0x106d92a in errnoBug (std.zig)
 if (is_debug) std.debug.panic("programmer bug caused syscall error: {t}", .{err});
 ^
~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Threaded.zig:1401:33: 0x106bae8 in errnoBug (std.zig)
 return Threaded.errnoBug(err);
 ^
~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Threaded.zig:7651:48: 0x1070f6d in dirRenamePreserveLinux (std.zig)
 .INVAL => |err| return syscall.errnoBug(err),
 ^
~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Threaded.zig:7415:59: 0x104c908 in dirRenamePreserve (std.zig)
 if (native_os == .linux) return dirRenamePreserveLinux(old_dir, old_sub_path, new_dir, new_sub_path);
 ^
~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Dir.zig:1025:39: 0x11c172b in renamePreserve (std.zig)
 return io.vtable.dirRenamePreserve(io.userdata, old_dir, old_sub_path, new_dir, new_sub_path);
 ^
~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/File/Atomic.zig:55:34: 0x11b0a7f in link (std.zig)
 try af.dir.renamePreserve(&tmp_sub_path, af.dir, af.dest_sub_path, io);
 ^
~/zig/test-inval/src/main.zig:7:15: 0x11ae5aa in main (main.zig)
 try f.link(init.io);
 ^
~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/start.zig:716:30: 0x11af07f in callMain (std.zig)
 return wrapMain(root.main(.{
 ^
~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/start.zig:190:5: 0x11ae441 in _start (std.zig)
 asm volatile (switch (native_arch) {
 ^
[1] 25817 IOT instruction (core dumped) zig run src/main.zig

I think the reason is that my home filesystem is ecryptfs, which isn't listed in the supported filesystems in rename(2):

RENAME_NOREPLACE requires support from the underlying
filesystem. Support for various filesystems was added as
follows:
 • ext4 (Linux 3.15);
 • btrfs, tmpfs, and cifs (Linux 3.17);
 • xfs (Linux 4.0);
 • Support for many other filesystems was added in Linux
4.9, including ext2, minix, reiserfs, jfs, vfat, and
bpf.

RENAME_NOREPLACE is used here, in std.Io.Threaded.dirRenamePreserveLinux, and this switch is what hits .INVAL:

while(true)switch(linux.errno(linux.renameat2(old_dir.handle,old_sub_path_posix,new_dir.handle,new_sub_path_posix,.{.NOREPLACE=true},))){

Running the program in /tmp (which stat -f -c %T /tmp says is ext2/ext3) runs without error.

@eshom the syscall error seems to be from the `b.addOptions()`, which uses `createFileAtomic` and `File.Atomic.link` Calling this gives the same error: ```zig pub fn main(init: std.process.Init) !void { var f = try std.Io.Dir.cwd().createFileAtomic(init.io, "./test.txt", .{}); defer f.deinit(init.io); try f.link(init.io); } ``` ``` thread 25817 panic: programmer bug caused syscall error: INVAL ~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Threaded.zig:14360:34: 0x106d92a in errnoBug (std.zig) if (is_debug) std.debug.panic("programmer bug caused syscall error: {t}", .{err}); ^ ~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Threaded.zig:1401:33: 0x106bae8 in errnoBug (std.zig) return Threaded.errnoBug(err); ^ ~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Threaded.zig:7651:48: 0x1070f6d in dirRenamePreserveLinux (std.zig) .INVAL => |err| return syscall.errnoBug(err), ^ ~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Threaded.zig:7415:59: 0x104c908 in dirRenamePreserve (std.zig) if (native_os == .linux) return dirRenamePreserveLinux(old_dir, old_sub_path, new_dir, new_sub_path); ^ ~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/Dir.zig:1025:39: 0x11c172b in renamePreserve (std.zig) return io.vtable.dirRenamePreserve(io.userdata, old_dir, old_sub_path, new_dir, new_sub_path); ^ ~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/Io/File/Atomic.zig:55:34: 0x11b0a7f in link (std.zig) try af.dir.renamePreserve(&tmp_sub_path, af.dir, af.dest_sub_path, io); ^ ~/zig/test-inval/src/main.zig:7:15: 0x11ae5aa in main (main.zig) try f.link(init.io); ^ ~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/start.zig:716:30: 0x11af07f in callMain (std.zig) return wrapMain(root.main(.{ ^ ~/zig/0.16.0-dev.2623+27eec9bd6/files/lib/std/start.zig:190:5: 0x11ae441 in _start (std.zig) asm volatile (switch (native_arch) { ^ [1] 25817 IOT instruction (core dumped) zig run src/main.zig ``` I think the reason is that my home filesystem is `ecryptfs`, which isn't listed in the supported filesystems in rename(2): ``` RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: • ext4 (Linux 3.15); • btrfs, tmpfs, and cifs (Linux 3.17); • xfs (Linux 4.0); • Support for many other filesystems was added in Linux 4.9, including ext2, minix, reiserfs, jfs, vfat, and bpf. ``` `RENAME_NOREPLACE` is used here, in `std.Io.Threaded.dirRenamePreserveLinux`, and this switch is what hits `.INVAL`: ```zig while (true) switch (linux.errno(linux.renameat2( old_dir.handle, old_sub_path_posix, new_dir.handle, new_sub_path_posix, .{ .NOREPLACE = true }, ))) { ``` Running the program in `/tmp` (which `stat -f -c %T /tmp` says is `ext2/ext3`) runs without error.
Contributor
Copy link

Thanks, ecryptfs is the key detail :)
I can now reliably reproduce this bug on my system with these steps:

  1. Install https://www.ecryptfs.org/
  2. Mount ecryptfs
mkdir encrypted
sudo mount -t ecryptfs encrypted/ encrypted/
  1. Compile:
pub fn main(init: std.process.Init) !void {
 var f = try std.Io.Dir.cwd().createFileAtomic(init.io, "./test.txt", .{});
 defer f.deinit(init.io);
 try f.link(init.io);
}

strace after adding .OPNOTSUPP as @freakman explained:

❯ strace -eopenat,renameat2 ./main
openat(AT_FDCWD, ".", O_RDWR|O_CLOEXEC|O_TMPFILE, 0666) = -1 EOPNOTSUPP (Operation not supported)
openat(AT_FDCWD, ".", O_RDONLY|O_CLOEXEC|O_PATH|O_DIRECTORY) = 3
openat(3, "fa107a5d14fe6572", O_WRONLY|O_CREAT|O_EXCL|O_TRUNC|O_CLOEXEC, 0666) = 4
renameat2(3, "fa107a5d14fe6572", 3, "test.txt", RENAME_NOREPLACE) = -1 EINVAL (Invalid argument)
thread 92138 panic: programmer bug caused syscall error: INVAL
[...stack trace...]

Without the patch, the program would just stop after the first openat

Thanks, `ecryptfs` is the key detail :) I can now reliably reproduce this bug on my system with these steps: 1. Install https://www.ecryptfs.org/ 2. Mount ecryptfs ``` mkdir encrypted sudo mount -t ecryptfs encrypted/ encrypted/ ``` 3. Compile: ``` pub fn main(init: std.process.Init) !void { var f = try std.Io.Dir.cwd().createFileAtomic(init.io, "./test.txt", .{}); defer f.deinit(init.io); try f.link(init.io); } ``` `strace` after adding `.OPNOTSUPP` as @freakman explained: ``` ❯ strace -eopenat,renameat2 ./main openat(AT_FDCWD, ".", O_RDWR|O_CLOEXEC|O_TMPFILE, 0666) = -1 EOPNOTSUPP (Operation not supported) openat(AT_FDCWD, ".", O_RDONLY|O_CLOEXEC|O_PATH|O_DIRECTORY) = 3 openat(3, "fa107a5d14fe6572", O_WRONLY|O_CREAT|O_EXCL|O_TRUNC|O_CLOEXEC, 0666) = 4 renameat2(3, "fa107a5d14fe6572", 3, "test.txt", RENAME_NOREPLACE) = -1 EINVAL (Invalid argument) thread 92138 panic: programmer bug caused syscall error: INVAL [...stack trace...] ``` Without the patch, the program would just stop after the first `openat`

Adding .OPPNOTSUP to this prong in lib/std/Io/Threaded.zig fixes the issue (line 4742):

good solution 👍

> Adding .OPPNOTSUP to this prong in lib/std/Io/Threaded.zig fixes the issue (line 4742): good solution 👍

Hi, I hit something similar last month. I use NFS for my repo work areas.

I'm new to Zig, so figured I'd start learning with 0.16 and hit build errors.
I needed more than the .OPNOTSUPP to get it working.

This is the patch I ended up with:

diff --git a/lib/std/Io/Dir.zig b/lib/std/Io/Dir.zig
index 3e38849f7f..c4d3908b6a 100644
--- a/lib/std/Io/Dir.zig
+++ b/lib/std/Io/Dir.zig
@@ -1795,6 +1795,8 @@ pub const CreateFileAtomicError = error{
 ReadOnlyFileSystem,
 /// The file attempted to be created is a running executable.
 FileBusy,
+ /// Linux TMPFILE on NFS
+ OperationUnsupported,
 } || Io.Dir.PathNameError || Io.Cancelable || Io.UnexpectedError;
 /// Create an unnamed ephemeral file that can eventually be atomically
diff --git a/lib/std/Io/Threaded.zig b/lib/std/Io/Threaded.zig
index 59382348e9..804431c116 100644
--- a/lib/std/Io/Threaded.zig
+++ b/lib/std/Io/Threaded.zig
@@ -4633,7 +4633,7 @@ fn dirCreateFileAtomic(
 try syscall.checkCancel();
 continue;
 },
- .ISDIR, .NOENT => {
+ .ISDIR, .NOENT, .OPNOTSUPP => {
 // Ambiguous error code. It might mean the file system
 // does not support O_TMPFILE. Therefore, we must fall
 // back to not using O_TMPFILE.
@@ -7514,12 +7514,13 @@ fn dirRenamePreserveLinux(
 const new_sub_path_posix = try pathToPosix(new_sub_path, &new_path_buffer);
 const syscall: Syscall = try .start();
+ var flags: linux.RENAME = .{ .NOREPLACE = true };
 while (true) switch (linux.errno(linux.renameat2(
 old_dir.handle,
 old_sub_path_posix,
 new_dir.handle,
 new_sub_path_posix,
- .{ .NOREPLACE = true },
+ flags,
 ))) {
 .SUCCESS => return syscall.finish(),
 .INTR => {
@@ -7544,7 +7545,21 @@ fn dirRenamePreserveLinux(
 .XDEV => return syscall.fail(error.CrossDevice),
 .ILSEQ => return syscall.fail(error.BadPathName),
 .FAULT => |err| return syscall.errnoBug(err),
- .INVAL => |err| return syscall.errnoBug(err),
+ .INVAL => |err| {
+ // NOREPLACE not valid on NFS, give up atomic in the name of working at all.
+ if (flags.NOREPLACE) {
+ const rc = openat_sym(new_dir.handle, new_sub_path_posix, .{.PATH = true}, @as(posix.mode_t, 0));
+ switch (posix.errno(rc)) {
+ .SUCCESS => closeFd(@intCast(rc)),
+ .NOENT => {
+ flags.NOREPLACE = false;
+ continue;
+ },
+ else => {},
+ }
+ }
+ return syscall.errnoBug(err);
+ },
 else => |err| return syscall.unexpectedErrno(err),
 };
 }

name -a : Linux big 6.18.12+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.18.12-1 (2026年02月17日) x86_64 GNU/Linux

Hi, I hit something similar last month. I use NFS for my repo work areas. I'm new to Zig, so figured I'd start learning with 0.16 and hit build errors. I needed more than the `.OPNOTSUPP` to get it working. This is the patch I ended up with: ``` diff --git a/lib/std/Io/Dir.zig b/lib/std/Io/Dir.zig index 3e38849f7f..c4d3908b6a 100644 --- a/lib/std/Io/Dir.zig +++ b/lib/std/Io/Dir.zig @@ -1795,6 +1795,8 @@ pub const CreateFileAtomicError = error{ ReadOnlyFileSystem, /// The file attempted to be created is a running executable. FileBusy, + /// Linux TMPFILE on NFS + OperationUnsupported, } || Io.Dir.PathNameError || Io.Cancelable || Io.UnexpectedError; /// Create an unnamed ephemeral file that can eventually be atomically diff --git a/lib/std/Io/Threaded.zig b/lib/std/Io/Threaded.zig index 59382348e9..804431c116 100644 --- a/lib/std/Io/Threaded.zig +++ b/lib/std/Io/Threaded.zig @@ -4633,7 +4633,7 @@ fn dirCreateFileAtomic( try syscall.checkCancel(); continue; }, - .ISDIR, .NOENT => { + .ISDIR, .NOENT, .OPNOTSUPP => { // Ambiguous error code. It might mean the file system // does not support O_TMPFILE. Therefore, we must fall // back to not using O_TMPFILE. @@ -7514,12 +7514,13 @@ fn dirRenamePreserveLinux( const new_sub_path_posix = try pathToPosix(new_sub_path, &new_path_buffer); const syscall: Syscall = try .start(); + var flags: linux.RENAME = .{ .NOREPLACE = true }; while (true) switch (linux.errno(linux.renameat2( old_dir.handle, old_sub_path_posix, new_dir.handle, new_sub_path_posix, - .{ .NOREPLACE = true }, + flags, ))) { .SUCCESS => return syscall.finish(), .INTR => { @@ -7544,7 +7545,21 @@ fn dirRenamePreserveLinux( .XDEV => return syscall.fail(error.CrossDevice), .ILSEQ => return syscall.fail(error.BadPathName), .FAULT => |err| return syscall.errnoBug(err), - .INVAL => |err| return syscall.errnoBug(err), + .INVAL => |err| { + // NOREPLACE not valid on NFS, give up atomic in the name of working at all. + if (flags.NOREPLACE) { + const rc = openat_sym(new_dir.handle, new_sub_path_posix, .{.PATH = true}, @as(posix.mode_t, 0)); + switch (posix.errno(rc)) { + .SUCCESS => closeFd(@intCast(rc)), + .NOENT => { + flags.NOREPLACE = false; + continue; + }, + else => {}, + } + } + return syscall.errnoBug(err); + }, else => |err| return syscall.unexpectedErrno(err), }; } ``` name -a : `Linux big 6.18.12+deb14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.18.12-1 (2026年02月17日) x86_64 GNU/Linux `
Contributor
Copy link

I was planning to try working on this today + tomorrow myself.
So now there are 2 test cases.

  • ecryptfs
  • NFS
    I hope that just running the existing unit tests on these file systems will trigger failures, otherwise I'll add test cases.
I was planning to try working on this today + tomorrow myself. So now there are 2 test cases. - ecryptfs - NFS I hope that just running the existing unit tests on these file systems will trigger failures, otherwise I'll add test cases.

I'm facing the same issue when building in a FUSE-mounted directory

: uname
╭──────────────────┬───────────────────────────────────────────────────────────╮
│ kernel-name │ Linux │
│ nodename │ laptop-huawei │
│ kernel-release │ 6.18.16 │
│ kernel-version │ #1-NixOS SMP PREEMPT_DYNAMIC Wed Mar 4 12:25:12 UTC 2026 │
│ machine │ x86_64 │
│ operating-system │ GNU/Linux │
╰──────────────────┴───────────────────────────────────────────────────────────╯

I'm facing the same issue when building in a FUSE-mounted directory >: uname ╭──────────────────┬───────────────────────────────────────────────────────────╮ │ kernel-name │ Linux │ │ nodename │ laptop-huawei │ │ kernel-release │ 6.18.16 │ │ kernel-version │ #1-NixOS SMP PREEMPT_DYNAMIC Wed Mar 4 12:25:12 UTC 2026 │ │ machine │ x86_64 │ │ operating-system │ GNU/Linux │ ╰──────────────────┴───────────────────────────────────────────────────────────╯
Contributor
Copy link

I've mentioned this in passing on Zulip, but maybe it's worth writing here too.
This issue and another one I've yet to open an issue about would have been caught if CI included running unit tests on less common filesystems (but still common enough, like NFS). Potentially more syscall related edge cases would be found this way.

Of course, that's up to ZSF / core team if they think it's worth the extra compute costs :-)

I've mentioned this in passing on Zulip, but maybe it's worth writing here too. This issue and another one I've yet to open an issue about would have been caught if CI included running unit tests on less common filesystems (but still common enough, like NFS). Potentially more syscall related edge cases would be found this way. Of course, that's up to ZSF / core team if they think it's worth the extra compute costs :-)
Contributor
Copy link

also happens on WSL with the 9p-mounted windows filesystems (discovered after updating my old pr to fix the other issues there)

also happens on WSL with the 9p-mounted windows filesystems (discovered after updating my old pr to fix the other issues there)
andrewrk added this to the 0.16.0 milestone 2026年03月21日 00:04:58 +01:00

fix landed in e938344100

fix landed in e938344100da959308aa27dee1295e5ce02efc30

@andrewrk @eshom, should I open a new issue?

It still doesn't build in an NFS mounted workspace on Linux, as I mentioned above. If I use the patch from above, it still builds. Given the changes made, I put what's left of the patch after the output of the failed build.

Building with tip e938344100

thread 810760 panic: programmer bug caused syscall error: INVAL
error return context:
/nfs-path-to/zig/lib/std/Io/Threaded.zig:4108:31: 0x123525a in dirAccessPosix (std.zig)
 .NOENT => return error.FileNotFound,
 ^
/nfs-path-to/zig/lib/std/Io/Dir.zig:439:5: 0x13604bb in access (std.zig)
 return io.vtable.dirAccess(io.userdata, dir, sub_path, options);
 ^
stack trace:
/nfs-path-to/zig/lib/std/Io/Threaded.zig:14045:34: 0x11e30ba in errnoBug (std.zig)
 if (is_debug) std.debug.panic("programmer bug caused syscall error: {t}", .{err});
 ^
/nfs-path-to/zig/lib/std/Io/Threaded.zig:1459:33: 0x11f1ac8 in errnoBug (std.zig)
 return Threaded.errnoBug(err);
 ^
/nfs-path-to/zig/lib/std/Io/Threaded.zig:7618:48: 0x1228bfb in dirRenamePreserveLinux (std.zig)
 .INVAL => |err| return syscall.errnoBug(err),
 ^
/nfs-path-to/zig/lib/std/Io/Threaded.zig:7382:59: 0x1227c28 in dirRenamePreserve (std.zig)
 if (native_os == .linux) return dirRenamePreserveLinux(old_dir, old_sub_path, new_dir, new_sub_path);
 ^
/nfs-path-to/zig/lib/std/Io/Dir.zig:1025:39: 0x144d4bb in renamePreserve (std.zig)
 return io.vtable.dirRenamePreserve(io.userdata, old_dir, old_sub_path, new_dir, new_sub_path);
 ^
/nfs-path-to/zig/lib/std/Io/File/Atomic.zig:55:34: 0x144cbcf in link (std.zig)
 try af.dir.renamePreserve(&tmp_sub_path, af.dir, af.dest_sub_path, io);
 ^
/nfs-path-to/zig/lib/std/Build/Step/Options.zig:493:29: 0x16611a6 in make (std.zig)
 atomic_file.link(io) catch |err| switch (err) {
 ^
/nfs-path-to/zig/lib/std/Build/Step.zig:278:33: 0x149db1f in make (std.zig)
 const make_result = s.makeFn(s, options);
 ^
/nfs-path-to/zig/lib/compiler/build_runner.zig:1339:26: 0x149b7ae in makeStep (build_runner.zig)
 } else if (s.make(.{
 ^
/nfs-path-to/zig/lib/std/Io.zig:1238:17: 0x149b2c5 in start (std.zig)
 _ = @as(Cancelable!void, @call(.auto, function, args_casted.*)) catch {};
 ^
/nfs-path-to/zig/lib/std/Io/Threaded.zig:552:22: 0x1248005 in start (std.zig)
 task.func(task.contextPointer());
 ^
/nfs-path-to/zig/lib/std/Io/Threaded.zig:1813:29: 0x12463e4 in worker (std.zig)
 runnable.startFn(runnable, &thread, t);
 ^
/nfs-path-to/zig/lib/std/Thread.zig:428:13: 0x1245f15 in callFn__anon_27432 (std.zig)
 @call(.auto, f, args);
 ^
/nfs-path-to/zig/lib/std/Thread.zig:1432:30: 0x1245cd0 in entryFn (std.zig)
 return callFn(f, self.fn_args);
 ^
/nfs-path-to/zig/lib/std/os/linux/x86_64.zig:105:5: 0x1245e35 in clone (std.zig)
 asm volatile (
 ^
error: the following build command terminated with signal ABRT:
.zig-cache/o/b9fe2493c5fccd6733ab8479b57013af/build /nfs-path-to/zig/build/zig2 lib /home/user/user/repos/zig .zig-cache /home/user/.cache/zig --seed 0xf90fbeec -Z4c43526e964e882b --prefix /home/user/user/repos/zig/build/stage3 -Dversion-string=0.16.0-dev.2979+e93834410 -Dtarget=native -Dcpu=native -Denable-llvm -Dconfig_h=/home/user/user/repos/zig/build/config.h -Dno-langref -Doptimize=ReleaseFast -Dstrip -Dno-lib
ninja: build stopped: subcommand failed.

The net patch given work done:

diff --git a/lib/std/Io/Dir.zig b/lib/std/Io/Dir.zig
index 3e38849f7f..c4d3908b6a 100644
--- a/lib/std/Io/Dir.zig
+++ b/lib/std/Io/Dir.zig
@@ -1795,6 +1795,8 @@ pub const CreateFileAtomicError = error{
 ReadOnlyFileSystem,
 /// The file attempted to be created is a running executable.
 FileBusy,
+ /// Linux TMPFILE on NFS
+ OperationUnsupported,
 } || Io.Dir.PathNameError || Io.Cancelable || Io.UnexpectedError;
 
 /// Create an unnamed ephemeral file that can eventually be atomically
diff --git a/lib/std/Io/Threaded.zig b/lib/std/Io/Threaded.zig
index 3f47272c12..fc91e87873 100644
--- a/lib/std/Io/Threaded.zig
+++ b/lib/std/Io/Threaded.zig
@@ -7585,12 +7585,13 @@ fn dirRenamePreserveLinux(
 const new_sub_path_posix = try pathToPosix(new_sub_path, &new_path_buffer);
 
 const syscall: Syscall = try .start();
+ var flags: linux.RENAME = .{ .NOREPLACE = true };
 while (true) switch (linux.errno(linux.renameat2(
 old_dir.handle,
 old_sub_path_posix,
 new_dir.handle,
 new_sub_path_posix,
- .{ .NOREPLACE = true },
+ flags,
 ))) {
 .SUCCESS => return syscall.finish(),
 .INTR => {
@@ -7615,7 +7616,21 @@ fn dirRenamePreserveLinux(
 .XDEV => return syscall.fail(error.CrossDevice),
 .ILSEQ => return syscall.fail(error.BadPathName),
 .FAULT => |err| return syscall.errnoBug(err),
- .INVAL => |err| return syscall.errnoBug(err),
+ .INVAL => |err| {
+ // NOREPLACE not valid on NFS, give up atomic in the name of working at all.
+ if (flags.NOREPLACE) {
+ const rc = openat_sym(new_dir.handle, new_sub_path_posix, .{.PATH = true}, @as(posix.mode_t, 0));
+ switch (posix.errno(rc)) {
+ .SUCCESS => closeFd(@intCast(rc)),
+ .NOENT => {
+ flags.NOREPLACE = false;
+ continue;
+ },
+ else => {},
+ }
+ }
+ return syscall.errnoBug(err);
+ },
 else => |err| return syscall.unexpectedErrno(err),
 };
 }
@andrewrk @eshom, should I open a new issue? It still doesn't build in an NFS mounted workspace on Linux, as I mentioned above. If I use the patch from above, it still builds. Given the changes made, I put what's left of the patch after the output of the failed build. Building with tip e938344100da959308aa27dee1295e5ce02efc30 ``` thread 810760 panic: programmer bug caused syscall error: INVAL error return context: /nfs-path-to/zig/lib/std/Io/Threaded.zig:4108:31: 0x123525a in dirAccessPosix (std.zig) .NOENT => return error.FileNotFound, ^ /nfs-path-to/zig/lib/std/Io/Dir.zig:439:5: 0x13604bb in access (std.zig) return io.vtable.dirAccess(io.userdata, dir, sub_path, options); ^ stack trace: /nfs-path-to/zig/lib/std/Io/Threaded.zig:14045:34: 0x11e30ba in errnoBug (std.zig) if (is_debug) std.debug.panic("programmer bug caused syscall error: {t}", .{err}); ^ /nfs-path-to/zig/lib/std/Io/Threaded.zig:1459:33: 0x11f1ac8 in errnoBug (std.zig) return Threaded.errnoBug(err); ^ /nfs-path-to/zig/lib/std/Io/Threaded.zig:7618:48: 0x1228bfb in dirRenamePreserveLinux (std.zig) .INVAL => |err| return syscall.errnoBug(err), ^ /nfs-path-to/zig/lib/std/Io/Threaded.zig:7382:59: 0x1227c28 in dirRenamePreserve (std.zig) if (native_os == .linux) return dirRenamePreserveLinux(old_dir, old_sub_path, new_dir, new_sub_path); ^ /nfs-path-to/zig/lib/std/Io/Dir.zig:1025:39: 0x144d4bb in renamePreserve (std.zig) return io.vtable.dirRenamePreserve(io.userdata, old_dir, old_sub_path, new_dir, new_sub_path); ^ /nfs-path-to/zig/lib/std/Io/File/Atomic.zig:55:34: 0x144cbcf in link (std.zig) try af.dir.renamePreserve(&tmp_sub_path, af.dir, af.dest_sub_path, io); ^ /nfs-path-to/zig/lib/std/Build/Step/Options.zig:493:29: 0x16611a6 in make (std.zig) atomic_file.link(io) catch |err| switch (err) { ^ /nfs-path-to/zig/lib/std/Build/Step.zig:278:33: 0x149db1f in make (std.zig) const make_result = s.makeFn(s, options); ^ /nfs-path-to/zig/lib/compiler/build_runner.zig:1339:26: 0x149b7ae in makeStep (build_runner.zig) } else if (s.make(.{ ^ /nfs-path-to/zig/lib/std/Io.zig:1238:17: 0x149b2c5 in start (std.zig) _ = @as(Cancelable!void, @call(.auto, function, args_casted.*)) catch {}; ^ /nfs-path-to/zig/lib/std/Io/Threaded.zig:552:22: 0x1248005 in start (std.zig) task.func(task.contextPointer()); ^ /nfs-path-to/zig/lib/std/Io/Threaded.zig:1813:29: 0x12463e4 in worker (std.zig) runnable.startFn(runnable, &thread, t); ^ /nfs-path-to/zig/lib/std/Thread.zig:428:13: 0x1245f15 in callFn__anon_27432 (std.zig) @call(.auto, f, args); ^ /nfs-path-to/zig/lib/std/Thread.zig:1432:30: 0x1245cd0 in entryFn (std.zig) return callFn(f, self.fn_args); ^ /nfs-path-to/zig/lib/std/os/linux/x86_64.zig:105:5: 0x1245e35 in clone (std.zig) asm volatile ( ^ error: the following build command terminated with signal ABRT: .zig-cache/o/b9fe2493c5fccd6733ab8479b57013af/build /nfs-path-to/zig/build/zig2 lib /home/user/user/repos/zig .zig-cache /home/user/.cache/zig --seed 0xf90fbeec -Z4c43526e964e882b --prefix /home/user/user/repos/zig/build/stage3 -Dversion-string=0.16.0-dev.2979+e93834410 -Dtarget=native -Dcpu=native -Denable-llvm -Dconfig_h=/home/user/user/repos/zig/build/config.h -Dno-langref -Doptimize=ReleaseFast -Dstrip -Dno-lib ninja: build stopped: subcommand failed. ``` The net patch given work done: ``` diff --git a/lib/std/Io/Dir.zig b/lib/std/Io/Dir.zig index 3e38849f7f..c4d3908b6a 100644 --- a/lib/std/Io/Dir.zig +++ b/lib/std/Io/Dir.zig @@ -1795,6 +1795,8 @@ pub const CreateFileAtomicError = error{ ReadOnlyFileSystem, /// The file attempted to be created is a running executable. FileBusy, + /// Linux TMPFILE on NFS + OperationUnsupported, } || Io.Dir.PathNameError || Io.Cancelable || Io.UnexpectedError; /// Create an unnamed ephemeral file that can eventually be atomically diff --git a/lib/std/Io/Threaded.zig b/lib/std/Io/Threaded.zig index 3f47272c12..fc91e87873 100644 --- a/lib/std/Io/Threaded.zig +++ b/lib/std/Io/Threaded.zig @@ -7585,12 +7585,13 @@ fn dirRenamePreserveLinux( const new_sub_path_posix = try pathToPosix(new_sub_path, &new_path_buffer); const syscall: Syscall = try .start(); + var flags: linux.RENAME = .{ .NOREPLACE = true }; while (true) switch (linux.errno(linux.renameat2( old_dir.handle, old_sub_path_posix, new_dir.handle, new_sub_path_posix, - .{ .NOREPLACE = true }, + flags, ))) { .SUCCESS => return syscall.finish(), .INTR => { @@ -7615,7 +7616,21 @@ fn dirRenamePreserveLinux( .XDEV => return syscall.fail(error.CrossDevice), .ILSEQ => return syscall.fail(error.BadPathName), .FAULT => |err| return syscall.errnoBug(err), - .INVAL => |err| return syscall.errnoBug(err), + .INVAL => |err| { + // NOREPLACE not valid on NFS, give up atomic in the name of working at all. + if (flags.NOREPLACE) { + const rc = openat_sym(new_dir.handle, new_sub_path_posix, .{.PATH = true}, @as(posix.mode_t, 0)); + switch (posix.errno(rc)) { + .SUCCESS => closeFd(@intCast(rc)), + .NOENT => { + flags.NOREPLACE = false; + continue; + }, + else => {}, + } + } + return syscall.errnoBug(err); + }, else => |err| return syscall.unexpectedErrno(err), }; } ```
Contributor
Copy link

confirming the continuing issue on my wsl-fix branch as well

confirming the continuing issue on my wsl-fix branch as well
Contributor
Copy link

I've updated this follow up issue here: #31542
There are several failures covered by the standard library tests, this included.

The fix was for TMPFILE and openat which closes this issue.
This other bug is with NOREPLACE in renameat2, which is called when TMPFILE is not supported so a temporary file is created and then renamed.

Retrying the syscall without the flag is a solution, it's also what mv does, personally I just wasn't comfortable making this design change in #31543 as a first PR.

Workaround for now:
If it makes sense for your usecase, either use Atomic.replace or Dir.rename directly. Those do not use NOREPLACE.

I've updated this follow up issue here: https://codeberg.org/ziglang/zig/issues/31542 There are several failures covered by the standard library tests, this included. The fix was for TMPFILE and `openat` which closes this issue. This other bug is with NOREPLACE in `renameat2`, which is called when TMPFILE is not supported so a temporary file is created and then renamed. Retrying the syscall without the flag is a solution, it's also what `mv` does, personally I just wasn't comfortable making this design change in #31543 as a first PR. Workaround for now: If it makes sense for your usecase, either use `Atomic.replace` or `Dir.rename` directly. Those do not use NOREPLACE.
Sign in to join this conversation.
No Branch/Tag specified
master
elfv2
spork8
restricted
0.16.x
panic-rewrite
parking-futex-lockfree
windows-Io-cleanup
Io-watch
ParseCommandLineOptions
windows-async-files
poll-ring
debug-file-leaks-differently
debug-file-leaks
ProcessPrng
elfv2-dyn
jobserver
threadtheft
io-threaded-no-queue
0.15.x
Io.net
comptime-allocator
restricted-function-pointers
cli
wasm-linker-writer
wrangle-writer-buffering
sha1-stream
async-await-demo
fixes
0.14.x
ast-node-methods
macos-debug-info
make-vs-configure
fuzz-macos
sans-aro
ArrayList-reserve
incr-bug
llvm-ir-nosanitize-metadata
ci-tarballs
ci-scripts
threadpool
0.12.x
new-pkg-hash
json-diagnostics
more-doctests
rework-comptime-mutation
0.11.x
ci-perf-comment
stage2-async
0.10.x
autofix
0.9.x
aro
hcs
0.8.x
0.7.x
0.16.0
0.15.2
0.15.1
0.15.0
0.14.1
0.14.0
0.12.1
0.13.0
0.12.0
0.11.0
0.10.1
0.10.0
0.9.1
0.9.0
0.8.1
0.8.0
0.7.1
0.7.0
0.6.0
0.5.0
0.4.0
0.3.0
0.2.0
0.1.1
0.1.0
Labels
Clear labels
abi/f32
abi/ilp32
abi/sf
accepted
This proposal is planned.
arch/21k
arch/6502
arch/aarch64
arch/alpha
arch/amdgcn
arch/arc
arch/arc32
arch/arc64
arch/arm
arch/avr
arch/bfin
arch/bpf
arch/colossus
arch/cris
arch/csky
arch/dlx
arch/epiphany
arch/fr30
arch/frv
arch/hexagon
arch/hppa
arch/hppa64
arch/ia64
arch/kalimba
arch/kvx
arch/lanai
arch/lm32
arch/loongarch32
arch/loongarch64
arch/m32r
arch/m68k
arch/m88k
arch/mcore
arch/microblaze
arch/mips
arch/mips64
arch/mmix
arch/moxie
arch/mrisc32
arch/msp430
arch/nds32
arch/ns32k
arch/nvptx
arch/or1k
arch/powerpc
arch/powerpc64
arch/propeller
arch/riscv32
arch/riscv64
arch/rl78
arch/rx
arch/s390x
arch/sh
arch/sparc
arch/sparc64
arch/spirv
arch/spu
arch/tricore
arch/v850
arch/vax
arch/vc4
arch/ve
arch/wasm
arch/x86
arch/x86_64
arch/xcore
arch/xtensa
autodoc
The web application for interactive documentation and generation of its assets.
backend/c
The C backend outputs C source code.
backend/llvm
The LLVM backend outputs an LLVM bitcode module.
backend/self-hosted
The self-hosted backends produce machine code directly.
binutils
Zig's included binary utilities: zig ar, zig dlltool, zig lib, zig ranlib, zig objcopy, and zig rc.
breaking
Implementing this issue could cause existing code to no longer compile or have different behavior.
build system
The Zig build system - zig build, std.Build, the build runner, and package management.
debug info
An issue related to debug information (e.g. DWARF) produced by the Zig compiler.
docs
An issue with documentation, e.g. the language reference or standard library doc comments.
error message
This issue points out an error message that is unhelpful and should be improved.
frontend
Tokenization, parsing, AstGen, ZonGen, Sema, Legalize, and Liveness.
fuzzing
An issue related to Zig's integrated fuzz testing.
incremental
Reuse of internal compiler state for faster compilation.
lib/c
This issue relates to Zig's libc implementation and/or vendored libcs.
lib/compiler-rt
This issue relates to Zig's compiler-rt library.
lib/cxx
This issue relates to Zig's vendored libc++ and/or libc++abi.
lib/std
This issue relates to Zig's standard library.
lib/tsan
This issue relates to Zig's vendored libtsan.
lib/ubsan-rt
This issue relates to Zig's ubsan-rt library.
lib/unwind
This issue relates to Zig's vendored libunwind.
linking
Zig's integrated object file and incremental linker.
miscompilation
The compiler reports success but produces semantically incorrect code.
os/android
os/contiki
os/dragonfly
os/driverkit
os/emscripten
os/freebsd
os/fuchsia
os/haiku
os/hermit
os/hurd
os/illumos
os/ios
os/linux
os/maccatalyst
os/macos
os/managarm
os/netbsd
os/ohos
os/openbsd
os/plan9
os/redox
os/rtems
os/serenity
os/tvos
os/uefi
os/visionos
os/wasi
os/watchos
os/windows
proposal
This issue suggests language modifications. If it also has the "accepted" label then it is planned.
release notes
This issue or pull request should be mentioned in the release notes.
testing
This issue is related to testing the compiler, standard library, or other parts of Zig.
zig cc
Zig as a drop-in C-family compiler.
zig fmt
The Zig source code formatter.
zig reduce
The Zig source code reduction tool.
bounty
https://ziglang.org/news/announcing-donor-bounties
bug
Observed behavior contradicts documented or intended behavior.
contributor-friendly
This issue is limited in scope and/or knowledge of project internals.
downstream
An issue with a third-party project that uses this project.
enhancement
Solving this issue will likely involve adding new logic or components to the codebase.
infra
An issue related to project infrastructure, e.g. continuous integration.
optimization
A task to improve performance and/or resource usage.
question
No questions on the issue tracker; use a community space instead.
regression
Something that used to work in a previous version stopped working
upstream
An issue with a third-party project that this project uses.
use case
Describes a real use case that is difficult or impossible, but does not propose a solution.
No labels
abi/f32
abi/ilp32
abi/sf
accepted
arch/21k
arch/6502
arch/aarch64
arch/alpha
arch/amdgcn
arch/arc
arch/arc32
arch/arc64
arch/arm
arch/avr
arch/bfin
arch/bpf
arch/colossus
arch/cris
arch/csky
arch/dlx
arch/epiphany
arch/fr30
arch/frv
arch/hexagon
arch/hppa
arch/hppa64
arch/ia64
arch/kalimba
arch/kvx
arch/lanai
arch/lm32
arch/loongarch32
arch/loongarch64
arch/m32r
arch/m68k
arch/m88k
arch/mcore
arch/microblaze
arch/mips
arch/mips64
arch/mmix
arch/moxie
arch/mrisc32
arch/msp430
arch/nds32
arch/ns32k
arch/nvptx
arch/or1k
arch/powerpc
arch/powerpc64
arch/propeller
arch/riscv32
arch/riscv64
arch/rl78
arch/rx
arch/s390x
arch/sh
arch/sparc
arch/sparc64
arch/spirv
arch/spu
arch/tricore
arch/v850
arch/vax
arch/vc4
arch/ve
arch/wasm
arch/x86
arch/x86_64
arch/xcore
arch/xtensa
autodoc
backend/c
backend/llvm
backend/self-hosted
binutils
breaking
build system
debug info
docs
error message
frontend
fuzzing
incremental
lib/c
lib/compiler-rt
lib/cxx
lib/std
lib/tsan
lib/ubsan-rt
lib/unwind
linking
miscompilation
os/android
os/contiki
os/dragonfly
os/driverkit
os/emscripten
os/freebsd
os/fuchsia
os/haiku
os/hermit
os/hurd
os/illumos
os/ios
os/linux
os/maccatalyst
os/macos
os/managarm
os/netbsd
os/ohos
os/openbsd
os/plan9
os/redox
os/rtems
os/serenity
os/tvos
os/uefi
os/visionos
os/wasi
os/watchos
os/windows
proposal
release notes
testing
zig cc
zig fmt
zig reduce
bounty
bug
contributor-friendly
downstream
enhancement
infra
optimization
question
regression
upstream
use case
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ziglang/zig#31231
Reference in a new issue
ziglang/zig
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?