Update wisp to v0.4.0#2
Conversation
|
Warning Review limit reached
More reviews will be available in 27 minutes and 29 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bumps the packaged wisp to v0.4.0 and the build toolchain to Zig 0.16.0.
ZIG_VERSION0.15.2 → 0.16.0 (with updated per-arch SHA256s from ziglang.org);WISP_VERSIONv0.2.2 → v0.4.0;WISP_COMMIT→cc7305345bd8a109487d9744fcc2df1eba03a6fc(the commit v0.4.0 points to; the build guard verifies it).0.2.2:0→0.4.0:0with release notes.wisp v0.4.0 replaces the thread-per-connection model with an epoll worker pool, keeping memory flat under connection churn (upstream #64).
Validation
Built the Dockerfile builder stage locally (amd64): Zig 0.16.0 downloaded + SHA verified, wisp v0.4.0 cloned + commit guard passed,
zig build -Doptimize=ReleaseFast -Dcpu=baselinesucceeded, and the resultingwispbinary runs.