-
Notifications
You must be signed in to change notification settings - Fork 15
xcube version upgrade to 0.9.1 and xcube-cci 0.9.0 #1018
Conversation
…hat arose from that change: * `TYPE_SPECIFIER_CUBE` replaced with `DATASET_TYPE` * `get_type_specifiers_for_data` replaced with `get_data_types_for_data` * Changed xcube `directory` configurations to `file`. * Changed Dockerfile. Is now completely based on quay.io/bcdev/xcube.
…ng this test fixed test test_ index. There were slight differences between expected and region. - Combined test and conda build workflows as the must run in sequence not in parallel. Docker shall only build after a successful unittest run. - Removed ignoring json validation deprecation notice in test_main as the issue causing this message has been resolved in xcube 0.9.1
- Removed truediv from data_frame.query call. Deprecated due to change in Python3 - Renamed usages of `np.float` to just `float` as `np.float` is deprecated - Ensured that variables re_year, first_months and first_days in aggregate are initialized - Increased xcube version to 0.9.1 - Removed pinning of jsonschema. Issue solved in xcube 0.9.1
Co-authored-by: Norman Fomferra <[email protected]>
Co-authored-by: Norman Fomferra <[email protected]>
TonioF
left a comment
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.
See my comments. Also, 'test_custom_region' in test_index.py fails on my local machine. I'd like to wait to see whether it works on Appveyor.
| username: ${{ secrets.QUAY_DOCKER_REPO_USERNAME }} | ||
| password: ${{ secrets.QUAY_DOCKER_REPO_PASSWORD }} | ||
| - uses: mr-smithers-excellent/docker-build-push@v5 | ||
| name: build-push-docker-image |
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.
| name: build-push-docker-image | |
| name: build-push-docker-image-release |
A tad more telling.
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.
Not sure, what the consequences of this would be, I took Helges changes... so the docker stuff is mostly his stuff :)
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.
I compared this to the workflow in xcube. There, a differentiation was made between latest and release, which I found more telling.
| def get_metadata_from_descriptor(descriptor: xcube_store.DataDescriptor) -> Dict: | ||
| metadata = dict(data_id=descriptor.data_id, | ||
| type_specifier=str(descriptor.type_specifier)) | ||
| type_specifier=str(descriptor.data_type)) |
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.
It would be best if we could get rid of the term "type_specifier" completely. This would require a change in cate-app, though, too.
Co-authored-by: Tonio Fincke <[email protected]>
Co-authored-by: Tonio Fincke <[email protected]>
Co-authored-by: Tonio Fincke <[email protected]>
…cja_xxx_xcube_0.9.1
When accepting this PR, cate will