Fixing Requirements File Generation#783
Conversation
…perator Signed-off-by: Eric Kerfoot <17726042+ericspod@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Walkthrough
ChangesRequirement formatting
Estimated code review effort: 2 (Simple) | ~10 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 `@ci/get_bundle_requirements.py`:
- Around line 86-92: Guard the bundle requirements parsing in
get_bundle_requirements.py so an empty stripped version never reaches
version[0], which can raise IndexError during requirements generation. In the
loop that builds version_line, add an explicit empty-string check after
version.strip() and handle it with a clear failure or skip path before
inspecting the first character. Also update the version formatting logic in this
block to avoid computing the default name==version string unless needed, and
keep the operator-detection behavior tied to the existing name, version, and
libs.append flow.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 5c382a02-b26e-4351-8f72-b1dd5058316b
📒 Files selected for processing (1)
ci/get_bundle_requirements.py
Signed-off-by: Eric Kerfoot <17726042+ericspod@users.noreply.github.com>
Description
This allows requirements files to be generated at test time from version in bundles which include range specifiers, eg "foo": ">=1.2.3". The bundle specification does not precisely say what the version specification should be thus it should be compatible with pip-style version specifiers of this format.
Status
Ready
Please ensure all the checkboxes:
./runtests.sh --codeformat.versionandchangeloginmetadata.jsonif changing an existing bundle.CONTRIBUTING.md).monai,pytorchandnumpyare correct inmetadata.json.eval_metricsof the provided weights and TorchScript modules.large_file.yml./home/your_name/for"bundle_root").Summary by CodeRabbit
<,>,=,!,~), it’s preserved without adding redundant==.