Prepare v0.5.2 release#89
Conversation
|
Warning Review limit reached
More reviews will be available in 53 minutes and 40 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ 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: Repository UI (base), Organization UI (inherited) Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughVersion 0.5.2 release update with documentation and configuration examples for per-backend STAT-missing probing, queue backpressure routing, and metrics logging intervals across Docker, Nix, and configuration files. Changesv0.5.2 Release Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Line 10: Confirm and correct the release date in the changelog header "##
[0.5.2] - 2026-06-10" to match the actual release/PR date; update that header to
the correct date (e.g., 2026-06-11 if the PR metadata is authoritative) or
verify with the release manager and set the date accordingly so the "## [0.5.2]
- ..." line is accurate.
In `@rust-toolchain.toml`:
- Line 2: The toolchain bump in rust-toolchain.toml (channel = "1.96.0") is fine
but the RustSec advisory lookup failed due to an unauthenticated GitHub API
call; add a step to run cargo audit (or RustSec) in CI or locally with
authenticated access: add a CI job that runs cargo audit against the workspace
after the toolchain bump and ensure the job provides a valid GitHub token (e.g.,
GITHUB_TOKEN) or points RUSTSEC_ADVISORY_DB at a checked-out advisory-db mirror
so the RustSec lookup can complete without HTTP 401 errors.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: f33fa23b-c61d-4399-808a-c0b7bd83c9e0
⛔ Files ignored due to path filters (2)
Cargo.lockis excluded by!**/*.lockflake.lockis excluded by!**/*.lock
📒 Files selected for processing (9)
CHANGELOG.mdCargo.tomlDockerfileconfig.full.tomldocker-compose.ymldocs/operator/configuration.mddocs/operator/operations.mdnix/module.nixrust-toolchain.toml
mjc
force-pushed
the
mjc/release-v0.5.2
branch
3 times, most recently
from
3f30d7d to
14d302e
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 21-26: The three bullet points in the "Added" section (lines
23-25) all begin with the word "Added", creating repetitive sentence structure
that reduces readability. Reword one or more of these bullet points to use
alternative phrasing such as "is now available", "provides", or similar
constructions that convey the same meaning while varying the sentence structure.
For example, rephrase the second bullet point about CPU pinning or the third
about rustix-based affinity handling to start differently, maintaining the
content's clarity and technical accuracy while improving the overall flow of the
changelog entry.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI (base), Organization UI (inherited)
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 9b49fc4e-9c01-418f-b572-43b38b785494
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (8)
CHANGELOG.mdCargo.tomlDockerfileconfig.full.tomldocker-compose.ymldocs/operator/configuration.mddocs/operator/operations.mdnix/module.nix
| ### Added | ||
|
|
||
| - Added per-backend `stat_missing` retry probing, so backends that correctly answer `STAT` with `430` can help retry missing articles faster. | ||
| - Added runtime CPU pinning support for multi-threaded workloads via a new `CpuPinning` runtime mode, using worker-thread startup hooks so pinned threads are the ones running proxy work. | ||
| - Added [`rustix`](https://docs.rs/rustix)-based affinity handling for Linux CPU pinning so we can remove the direct `nix` pinning dependency path. | ||
|
|
There was a problem hiding this comment.
🧹 Nitpick | 🔵 Trivial | 💤 Low value
Reduce repetitive sentence beginnings in the "Added" section.
Lines 23–25 all begin with "Added". Consider rewording one or more to improve readability, e.g., "Per-backend stat_missing retry probing is now available…" or "Runtime CPU pinning support is now available…".
🧰 Tools
🪛 LanguageTool
[style] ~24-~24: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...n help retry missing articles faster. - Added runtime CPU pinning support for multi-t...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
[style] ~25-~25: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...eads are the ones running proxy work. - Added rustix-base...
(ENGLISH_WORD_REPEAT_BEGINNING_RULE)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` around lines 21 - 26, The three bullet points in the "Added"
section (lines 23-25) all begin with the word "Added", creating repetitive
sentence structure that reduces readability. Reword one or more of these bullet
points to use alternative phrasing such as "is now available", "provides", or
similar constructions that convey the same meaning while varying the sentence
structure. For example, rephrase the second bullet point about CPU pinning or
the third about rustix-based affinity handling to start differently, maintaining
the content's clarity and technical accuracy while improving the overall flow of
the changelog entry.
Source: Linters/SAST tools
1 participant
This adds the
v0.5.2changelog section and updates the release notes to cover:stat_missingprobingThe branch has been pushed and is ready for review.
Summary by CodeRabbit
STATprobing (STAT_MISSING) to prefetch missing articles after430.