fix: use i64 for RateLimiter timestamps instead of i128

YUX · claude · YUX · commit c4f13362675b · 2025-11-09T21:44:32.000+08:00
x86_64 Linux does not support atomic operations on 128-bit integers. Changed timestamp fields from i128 to i64, which is sufficient for nanosecond precision until year 2262. This fixes cross-compilation for x86_64-linux-gnu and x86_64-linux-musl targets in the Release workflow. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/src/common.zig b/src/common.zig
@@ -266,16 +266,16 @@ pub fn recvAllFromFd(fd: posix.fd_t, buffer: []u8) !void {
 pub const RateLimiter = struct {
     tokens: std.atomic.Value(u32),
     max_tokens: u32,
-    refill_interval_ns: i128,
-    last_refill: std.atomic.Value(i128),
+    refill_interval_ns: i64,
+    last_refill: std.atomic.Value(i64),
 
     /// Create a rate limiter allowing `max_per_second` operations per second
     pub fn init(max_per_second: u32) RateLimiter {
         return .{
             .tokens = std.atomic.Value(u32).init(max_per_second),
             .max_tokens = max_per_second,
-            .refill_interval_ns = @divTrunc(std.time.ns_per_s, max_per_second),
-            .last_refill = std.atomic.Value(i128).init(std.time.nanoTimestamp()),
+            .refill_interval_ns = @intCast(@divTrunc(std.time.ns_per_s, max_per_second)),
+            .last_refill = std.atomic.Value(i64).init(@intCast(std.time.nanoTimestamp())),
         };
     }
 
@@ -302,7 +302,7 @@ pub const RateLimiter = struct {
         }
 
         // Refill if needed
-        const now = std.time.nanoTimestamp();
+        const now: i64 = @intCast(std.time.nanoTimestamp());
         const last = self.last_refill.load(.monotonic);
         const elapsed = now - last;
 
