[caliper] orchestration: export: make the workspace config mandatory#107
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Warning Review limit reached
Next review available in: 3 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 selected for processing (3)
📝 WalkthroughWalkthroughThe multi-run export path in export.py now requires a non-empty workspace value from the merged MLflow config, raising a ValueError if absent, and prints the raw workspace value in verbose output. The rhaiis config.yaml adds a workspace value for the MLflow export backend. ChangesMandatory MLflow Workspace
Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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: 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 `@projects/caliper/orchestration/export.py`:
- Around line 338-340: The workspace validation in _run_multi_run_export raises
a bare ValueError before the existing CLI error handling kicks in, so replace it
with the same user-facing pattern used elsewhere in the export flow (for example
in artifacts_export_run.py): emit the message with click.echo(..., err=True) and
return a non-zero status instead of letting the exception escape. Use
_run_multi_run_export and the workspace check to locate the change.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: 21f0f4a6-0874-4001-8af8-077f11d397cd
📒 Files selected for processing (2)
projects/caliper/orchestration/export.pyprojects/rhaiis/orchestration/config.yaml
|
/test fournos skeleton collect_cluster_info |
🟢 Execution of
|
🟢 Submission of
|
🟢 Execution of
|
|
/test fournos skeleton collect_cluster_info |
🟢 Execution of
|
🟢 Submission of
|
|
/test fournos skeleton collect_cluster_info |
🟢 Execution of
|
🟢 Submission of
|
|
/test fournos skeleton collect_cluster_info |
🟢 Execution of
|
🔴 Submission of
|
|
/test fournos skeleton collect_cluster_info |
🔴 Submission of
|
…ge in the notification
|
/test fournos skeleton collect_cluster_info |
🔴 Submission of
|
|
/test fournos skeleton collect_cluster_info |
🟢 Execution of
|
🟢 Submission of
|
Summary by CodeRabbit