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
DM-36517: Add support for ChainedDatastore.export() #743
Conversation
fa9b225
to
1388ee2
Compare
Codecov ReportBase: 84.88% // Head: 84.94% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #743 +/- ##
==========================================
+ Coverage 84.88% 84.94% +0.06%
==========================================
Files 257 257
Lines 33342 33431 +89
Branches 5667 5692 +25
==========================================
+ Hits 28302 28398 +96
+ Misses 3807 3804 -3
+ Partials 1233 1229 -4
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
8564073
to
373ec5c
Compare
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 good, few minor questions.
f50644a
to
cd3f212
Compare
This method can run the knows() method in bulk.
Adjust the test inheritance such that the export tests are now run for the ChainedDatastore
This required we change the exception type in some failure modes to match that raise by butler.export.
Also include test with a missing dataset.
This requires that auto be converted to None if no directory is given. FileDatastore and ChainedDatastore already had "auto" as a default.
We had not noticed it was wrong until the pyyaml types package added an annotation for loader.construct_mapping()
369dbd9
to
fdb33ad
Compare
Checklist
doc/changes