Conversation
|
Warning Review limit reached
Next review available in: 55 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughStorage configuration now accepts an optional folder name, normalizes it in the shared path builder, and propagates it to Azure, GCS, Google Drive, local, and S3 uploads. Tests cover default and custom folders. Docker Compose also updates ChangesFolder-aware storage paths
Compose environment update
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
✨ 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 |
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 `@docker-compose.yml`:
- Line 24: Remove the hardcoded EDGE_KEY value from the Compose configuration
and replace it with deployment-environment injection, such as an
environment-variable reference. Ensure src/settings.rs and src/core/context.rs
continue receiving the key through the existing EDGE_KEY configuration, and
rotate or revoke the currently committed credential.
In `@src/utils/file.rs`:
- Around line 50-57: Validate the folder name once in full_file_path: reject
control characters, dot segments, and unsupported separators, or explicitly
canonicalize nested paths before constructing the provider path;
src/utils/file.rs lines 50-57 require this change. In
src/services/storage/providers/local.rs line 41, handle HeaderValue::from_str
failure explicitly and remove the downstream unwrap panic.
🪄 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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 26022c90-f7b4-4afe-926e-eb626950bb78
📒 Files selected for processing (9)
docker-compose.ymlsrc/services/api/models/agent/status.rssrc/services/storage/providers/azure_blob/mod.rssrc/services/storage/providers/google_cloud_storage/mod.rssrc/services/storage/providers/google_drive/mod.rssrc/services/storage/providers/local.rssrc/services/storage/providers/s3/mod.rssrc/tests/utils/file_tests.rssrc/utils/file.rs
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary by CodeRabbit
New Features
backupsused when no custom folder is specified.Bug Fixes
Tests