release(v0.7.1): SQ8 CPU-storm fix + deterministic replica TTL - #336
Conversation
Patch release folding in the two follow-ups disclosed in the v0.7.0 tag notes, both already merged to main: - Vector SQ8/TQ code-size mis-dispatch CPU error-storm (#73, #334): bits=8 fell outside TurboQuant's 1..=4 range, so code_bytes_per_vector returned 0 while emitting a tracing::error! on every call on the hot memory-accounting path. - Deterministic replica TTL (#71, #335): master-side absolute rewrite of relative-expiry commands (EXPIRE/PEXPIRE/SETEX/PSETEX/SET EX-PX/GETEX -> PEXPIREAT/SET PXAT) using the per-tick cached clock (#71a), plus role-gated active expiry so a replica converges on the master's authoritative removal instead of racing its own TTL sweep (#71b). Release mechanics: - Cargo.toml + Cargo.lock: 0.7.0 -> 0.7.1 - CHANGELOG.md: rolled [Unreleased] Fixed bullets under new [0.7.1] heading - RELEASES.md: prepended v0.7.1 ledger entry (release-ledger CI gate) - docs/guides/clustering.md: replica-TTL warning flipped to "deterministic since v0.7.1" note (absolute-rewrite + role-gated expiry now shipped) - docs/PRODUCTION-CONTRACT.md: corrected stale "keyspace-notif deferred to v0.7.1" line (this patch ships only SQ8 + TTL) author: Tin Dang <tindang.ht97@gmail.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Warning Review limit reached
Next review available in: 20 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
✨ 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 |
2 participants
Patch release folding in the two follow-ups disclosed in the v0.7.0 tag notes — both already merged to
main(#334, #335). This PR is the version/ledger/docs roll-up.Contents
0.7.0→0.7.1[Unreleased]### Fixedbullets (SQ8 feat(v0.1.5): Moon Console — interactive data client #73 + replica TTL perf: PR #43 recovery — ACL caching, inline SET, NEON SIMD #71) under a new## [0.7.1] — 2026-07-15heading;[Unreleased]now empty.[0.7.0]heading preserved.## v0.7.1ledger entry (satisfies the release-ledger CI gate inrelease.yml).KEYSPACE-NOTIF-01line that said the feature was "deferred to v0.7.1" — this patch ships only SQ8 + TTL, so keyspace notifications move to a later release.Shipped fixes (already on main)
code_bytes0 + per-calltracing::error!).Post-merge (paused for owner OK)
Tag
v0.7.1on the merge commit →release.ymlruns (release-ledger gate, contract report, 8-target build + sign + GH release + docker).author: Tin Dang tindang.ht97@gmail.com