Feature/upgrade pangeo extensions #145
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marjo-luc
approved these changes
Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Extensions need to be upgraded in jupyterlab/pangeo/environment.yml to match jupyterlab/shared/environment.yml
Can test with this image: 'mas.dit.maap-project.org/root/maap-workspaces/jupyterlab/pangeo:upgrade-pangeo-extensions'
Sorry for missing this before, but this should be merged by the release
I can do all my smoke tests again for the pangeo image once we deploy into UAT
A couple times getting presigned s3 urls was failing, but that was happening in the existing pangeo develop image as well, so I created this ticket here: MAAP-Project/Community#1105
Both this ticket, and the pangeo kernel issues should be addressed before our release and I will work on these tomorrow