-
Notifications
You must be signed in to change notification settings - Fork 1
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
Track and test upgrade of pangeo-notebook image in veda-jh-environments #41
Comments
|
@ranchodeluxe thanks for the updates. Perhaps we should merge these instructions into that documentation and / or create an issue template for future upgrades. |
@abarciauskas-bgse are you going to do the PR to bump the pangeo image? the stac_ipyleaflet fix is a simple version bump too (current version is broken), and pypi install of lonboard should be straight forward if @kylebarron finished the new release. But I don't know if we want to mix all these things. Or test one at a time, then do the PR to 2i2c with everything? |
I'm hoping to release a new minor version of lonboard tomorrow (depending on time around zarr sprint) |
yes, thanks for the nudge: #42 |
@ranchodeluxe do it |
PR in: 2i2c-org/infrastructure#3788 |
Description
We would like to upgrade the pangeo-notebook image used by the VEDA JupyterHub so we get an updated version of xarray to solve an issue with reading chunks from h5netcdf (see pydata/xarray#8691). This may also resolve some of the features of interest in https://github.com/NASA-IMPACT/veda-analytics/issues/94.
@wildintellect mentioned there was an issue with moving to JupyterLab 4, which is a part of this updated pangeo-notebook image https://github.com/pangeo-data/pangeo-docker-images/blob/2024.01.23/pangeo-notebook/packages.txt#L270C1-L270C19
Checklist:
pangeo-notebook
image tag: https://github.com/NASA-IMPACT/veda-jh-environments/blob/main/docker-images/base/pangeo-notebook/Dockerfile#L1 to have the updated image tagpangeo/pangeo-notebook:2024.01.23
ONBUILD
commands in docker are only heritable for the immediate child. And our "custom" singleuser images will include dependencies that we want to be picked up with the adjacentenvironment.yml
The text was updated successfully, but these errors were encountered: