Artifact dd3992bfc8da12e09a018c4697e38ddf79d07e225405af448ecca1ebefc3ea0c:
- File
build.zig.zon
— part of check-in
[a469147254]
at
2026-07-25 14:51:11
on branch trunk
— Release zit 0.1.3
A serving release over 0.1.2. Where 0.1.2 made a large repository cloneable, 0.1.3 makes serving one fast and lean.
A server against a large repository comes up immediately: the listener opens before the repository is read, so a client queues in the accept backlog while the server primes rather than being refused during a startup a large store made long. A push no longer stalls inside its own reply deadline; the snapshot rebuild it triggers now runs between connections. Serving reads the repository through an on-demand log-offset index rather than a resident copy, so peak memory to serve a 67,499-artifact repository fell from about 157 MB to about 32 MB, with clones byte-identical to before.
Also: the end-to-end suite is safe to run concurrently with itself (fresh loopback ports), and the unclassifiable-artifact tolerance rule is now covered by deterministic simulation and an end-to-end scenario. (user: dmestas, size: 347) [annotate] [blame] [check-ins using]
.{ .name = .zit, .version = "0.1.3", .fingerprint = 0x4570515ffc0991f4, // Changing this has security and trust implications. .minimum_zig_version = "0.16.0", .dependencies = .{}, .paths = .{ "build.zig", "build.zig.zon", "src", "docs/rfcs", "README.md", "LICENSE", }, }