Bump OpenZGY to 0.2.970
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [No]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Updates description?
SDAPI and OpenZGY updated to the latest version. SDAPI - 3.18.459, OpenZGY - 0.2.970
Merge request reports
Activity
requested review from @imonteiro
enabled an automatic merge when the pipeline for 87e0a6ef succeeds
Hello @Zakhar ,
We've noticed that with this segy-zgy dag image, the conversion succeeds but the converted artefact is missing from the record:
Master dag image: https://osdu-glab.msft-osdu-test.org/airflow2/log?dag_id=segy-to-zgy-conversion&task_id=segy-to-zgy&execution_date=2023-03-23T14%3A15%3A45.564127%2B00%3A00
Dag image from this branch: https://osdu-ship.msft-osdu-test.org/airflow2/log?dag_id=segy-to-zgy-conversion&task_id=segy-to-zgy&execution_date=2023-03-14T12%3A32%3A00.040867%2B00%3A00
Responses from both the converted records are attached.record_retrieve_bumped_version.json
Hi @deepapathak,
Can you paste the relevant part of the logs? I don't have access to this airflow instance. This PR is updating the client libraries OpenZGY to version 0.2.970 and SDAPI to version 3.18. It is not expected to have any effect on records being created, since these libraries are only used for bulk data.
added 1 commit
- 6d8a0f6d - build: skip stage failling for more than 6 months
enabled an automatic merge when the pipeline for 6d8a0f6d succeeds
mentioned in commit c5b82c2d
changed milestone to %M17 - Release 0.20