Intake is going through some changes. These have brought to light some unnecessary definitions within .yaml files that are causing issues with the newer version of intake. See #415
The propose change allows to go from, for example :
This change is backwards compatible with intake versions 0.7, which is the current version installed on Sciserver Oceanography environment, and the current version being pinned right now.
Without the proposed change above, intake version 2.0 cannot open the yaml file.
What am I proposing
The fix is very simple but involves 2 steps for all tests in CI to pass.
1) I need to first modify the file: .oceanspy/main/sciserver_catalogs/catalog_xarray.yaml, locally and then remotely with its own PR. OceanSpy reads this file from GH associated with the previous / most recent PR HERE.
2) Change local files. Unpin intake a separate PR.
If i don't do step 1) first, step 2) will show fail CI test which will be missleading.
Description
Intake is going through some changes. These have brought to light some unnecessary definitions within .yaml files that are causing issues with the newer version of intake. See #415
The propose change allows to go from, for example :
old behavior
to NEW BEHAVIOR
This change is backwards compatible with intake versions
0.7
, which is the current version installed on Sciserver Oceanography environment, and the current version being pinned right now.Without the proposed change above, intake version
2.0
cannot open the yaml file.What am I proposing
The fix is very simple but involves 2 steps for all tests in CI to pass.
1) I need to first modify the file:
.oceanspy/main/sciserver_catalogs/catalog_xarray.yaml
, locally and then remotely with its own PR. OceanSpy reads this file from GH associated with the previous / most recent PR HERE.2) Change local files. Unpin
intake
a separate PR.If i don't do step
1)
first, step2)
will show fail CI test which will be missleading.FYI: OceanSpy code is not changing at all.