-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENH] Allow unrecognized pipeline names and versions in processing status file #401
Conversation
Reviewer's Guide by SourceryThis PR updates the pipeline validation logic to be more flexible by allowing unrecognized pipeline names and versions in the processing status file. Instead of failing immediately when encountering unrecognized entries, the system now emits warnings and continues processing with the recognized pipelines/versions, only erroring out if no valid pipeline-version combinations are found. Class diagram for updated pipeline validation logicclassDiagram
class DerivativeUtils {
+list get_recognized_pipelines(Iterable~str~ pipelines)
+tuple~list, list~ classify_pipeline_versions(str pipeline, Iterable~str~ versions)
+void check_at_least_one_pipeline_version_is_recognized(pd.DataFrame status_df)
}
class Mappings {
+dict KNOWN_PIPELINE_URIS
+dict KNOWN_PIPELINE_VERSIONS
}
DerivativeUtils --> Mappings : uses
class CLI {
+void derivatives(pd.DataFrame status_df)
}
CLI --> DerivativeUtils : uses
File-Level Changes
Assessment against linked issues
Possibly linked issues
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #401 +/- ##
==========================================
+ Coverage 98.42% 98.56% +0.14%
==========================================
Files 18 18
Lines 1016 1116 +100
==========================================
+ Hits 1000 1100 +100
Misses 16 16 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @alyssadai - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟡 General issues: 2 issues found
- 🟢 Security: all looks good
- 🟡 Testing: 3 issues found
- 🟡 Complexity: 1 issue found
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @alyssadai - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟡 Testing: 2 issues found
- 🟡 Complexity: 1 issue found
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
@sourcery-ai review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @alyssadai - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟡 Complexity: 1 issue found
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @alyssadai for the PR. Looks like sourcery was trying to filibuster your work here - can't let that happen!
I have some clarity points so not approving yet, but they are pretty small. Mainly
- what's most helpful to show user if they have bad pipeline names or versions
- make tests easier for human brain
lmk what you think
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
edit: not sure where this ghost review is from 👀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @alyssadai, I don't see any changes since the last review. Have you maybe not pushed your changes yet?
Hey @surchs, you're totally right, sorry about that! You should be able to see the changes now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great @alyssadai!
🧑🍳
🚀 PR was released in |
Changes proposed in this pull request:
For reviewer: Sourcery was super verbose on this PR because it seemingly reviewed it twice (I accidentally marked the PR ready for review before I was ready, and then once I converted to draft and then back to ready for review, the old comments stuck around even though several were no longer applicable). Not sure how to make Sourcery auto-resolve old reviews - I attempted to do it using a command but that only triggered yet another review 😬 To make this PR easier to read, I've left only the most recent set of comments unresolved.
Checklist
This section is for the PR reviewer
[ENH]
,[FIX]
,[REF]
,[TST]
,[CI]
,[MNT]
,[INF]
,[MODEL]
,[DOC]
) (see our Contributing Guidelines for more info)skip-release
(to be applied by maintainers only)Closes #XXXX
For new features:
For bug fixes:
Summary by Sourcery
Enhance the processing status file handling by allowing unrecognized pipeline names and versions, emitting warnings instead of errors when some are unrecognized, and ensuring at least one recognized pipeline-version combination is present. Update tests to cover these scenarios.
Enhancements:
Tests:
Summary by Sourcery
Enhance the processing status file handling by allowing unrecognized pipeline names and versions, emitting warnings instead of errors when some are unrecognized, and ensuring at least one recognized pipeline-version combination is present. Update tests to cover these scenarios.
Enhancements:
Tests: