0.3.64: adopt ciris-server 0.5.200 - #75
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
The pin moves v0.5.199 -> v0.5.200; the substrate is unchanged through it, so the lock moves exactly two entries (ciris-server, ciris-lens-core). Rebased over 0.3.63 (#72, the in-binary arena cap), hence 0.3.64. 0.5.200 is the pass that streams. The canonical's read API had stopped accepting for 8–40 s every 15 minutes because two node constants fired in the same second (CIRISServer#553): the equivocation pass now streams a page at a time into a claim index, walks the tier from a persisted cursor, digests off the runtime workers and logs its cost; the two timers are de-phased; the capacity scorer skips its pass while the corpus is unchanged. The server now also caps the glibc arenas in-process, the same move 0.3.63 made here, with a loopback-only trim door behind --diagnostics (CIRISServer#552). No source change: clippy -D warnings clean, fmt clean, 114/114 tests. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0132ELwj5JU6t4jEKpwH9bJ7
emooreatx
force-pushed
the
chore/adopt-ciris-server-0.5.200
branch
from
September 7, 2026 03:00
dfbe937 to
9b41246
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One pin; the lock moves exactly two entries (ciris-server, ciris-lens-core). No source change:
cargo clippy --all-targets -- -D warningsclean, fmt clean, 114/114 tests. Rebased over #72 (0.3.63, the in-binary arena cap), so this is 0.3.64.Why 0.5.200. The pass that streams (CIRISServer#554). The canonical's read API had stopped accepting for 8–40 s every 15 minutes because two node constants fired in the same second (CIRISServer#553): the equivocation pass now streams a page at a time into a claim index, walks the tier from a persisted cursor (it used to rescan the same 4,096 rows forever), digests off the runtime workers and logs its cost; the two timers are de-phased; the capacity scorer skips its pass while the corpus is unchanged (it was 30–43 s of every 60 s, authoring nothing). The server now also caps the glibc arenas in-process — the same move #72 made here — with a loopback-only trim door behind
--diagnostics(CIRISServer#552).Release: CIRISServer v0.5.200 tagged at a801ee3; PyPI publish running off the tag (this pin is the git tag, so it does not wait on PyPI). Eric wants a fresh soak on this cut.
🤖 Generated with Claude Code
https://claude.ai/code/session_0132ELwj5JU6t4jEKpwH9bJ7