-
Notifications
You must be signed in to change notification settings - Fork 6
upgrade to odc>1.9 #195
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
upgrade to odc>1.9 #195
Conversation
for more information, see https://pre-commit.ci
Co-authored-by: Emma Ai <emma.ai@ga.gov.au>
updates: - [github.com/adrienverge/yamllint.git: v1.37.0 → v1.37.1](https://github.com/adrienverge/yamllint.git/compare/v1.37.0...v1.37.1) Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #195 +/- ##
===========================================
+ Coverage 81.47% 81.50% +0.03%
===========================================
Files 50 53 +3
Lines 4604 4824 +220
===========================================
+ Hits 3751 3932 +181
- Misses 853 892 +39 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
A couple of minor tweaks and/or clarifications requested. Otherwise looking great!
tests on the older docker image statistician test and push won't as it has old dependencies.
It should be possible to get this working before merge, and doing so would make me feel a bit more comfortable - we do always run stats in a docker container after all. Happy to have different docker image tags for 1.8 and 1.9 branches if that helps.
It is possible but it'll defy the purpose of failing it in the long run. the docker image won't be published/pushed if failure after merging, which guarantees:
|
OK I was confused about how the github actions work. Agreed. |
dataset.metadata_doc, skip_validation=True | ||
) | ||
# it will grab all useful input dataset preperties | ||
dataset_assembler._inherit_properties_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.
Is this still necessary now that we're no longer passing dataset_assembler
the dataset doc?
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.
the serialised dataset doc is still passed to dataset_assembler to grab some properties. I broke the same functionality in 3 parts,
- validate classifier
401
- inherit properties from source
418
- record lineage
422
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.
But doesn't this mean that we're treating the one dataset as both the source the derived dataset? Or does the distinction not particularly matter in this case
tree = LineageTree.from_eo3_doc(ds.metadata_doc) | ||
lineage |= ( | ||
tree.child_datasets() if tree.child_datasets() else {tree.dataset_id} | ||
) |
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.
Oh yeah, that's much better.
As the tile. Current
develop
is tagged asdevelop_1.8
for record.integrate_1.9
wrt update onodc.*>1.9
numexpr
related functionality back toodc-algo
native_loading
fromodc-algo
atm, further discussion on shuffling the code againNote that:
run code check
should passstatistician test and push
won't as it has old dependencies.