-
Notifications
You must be signed in to change notification settings - Fork 4
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
Avoid using python 3.12 for now #13
Conversation
👋 Thanks for opening this PR! The Cookbook will be automatically built with GitHub Actions. To see the status of your deployment, click below. |
This notebook relies on Dask parallelism to be responsive. With four workers, it should complete in under ten minutes. The GitHub build timeout value of 5 minutes is probably a bit too low for this notebook. |
I remember talking with @brian-rose about running this notebook with a larger timeout value, and performing the nightly build action only once a week. The nightly build workflow is still set up to run on Sundays at midnight. I don't know how to increase the timeout value for this notebook, however. |
With lower data requirements, the notebook ran in just over 6 minutes. I don't know how the 5 minute timeout limit was circumvented this time, but...yay? |
This cookbook is currently set to a one-hour timeout, see this line in the config file: na-cordex-viz-cookbook/_config.yml Line 13 in 2b07b14
|
Thanks for checking! I guess this timeout error from yesterday was a fluke then? https://github.com/ProjectPythia/na-cordex-viz-cookbook/actions/runs/7280739398/job/19839811580 |
Maybe! The notebook execution part of the builds are running on the Pythia binder, not on GitHub actions. Sometimes the lengthiest part of a Binder run is building the image, which needs to happen if there are any changes the environment file (which is the case in this PR). We're also aiming to have better support for dask workers on demand for bigger builds through this Binder, but we're not there yet. |
It's possible that there are still some hidden timeout conditions being passed through binderbot (the command line tool we are using the route the notebook execution to the Binder). Fixing up that software is also a 2024 priority. I don't currently have a good explanation for why you got a 5-minute timeout in one case but not others. |
Okay, I understand. We have another failure data point now. I removed an unneeded "import pprint" in the notebook and we got another Binder build error. I'm pretty sure the notebook is working now, despite the error. |
Hmm different error this time. I will see what the old "unplug and plug back in" cycle accomplishes. |
Unrelated failure. Now Binder is looking for the repo under my user name:
This is a bug in our workflows. It shouldn't matter who clicked the "reopen" button. I'll try to document this elsewhere. @bonnland you might try your own "close and reopen" and see what happens. |
Actually this failure is for the same reason as ProjectPythia/cookbook-actions#79 |
The failure now looks like
I got the same failure trying to run an interactive Binder session with a different repo. There's something wrong with the Binder currently, unrelated (as far as I can tell) to this PR. I will check to @ktyle to see if we can find out what's up with the Binder. |
It seems the Binder failure may be related to current maintenance on Jetstream2 where the Binder is running. @bonnland sorry for the multiple hiccups, but you should try closing and reopening again later. |
It looks like the checks passed. Should I merge to main, or let someone else when the timing is better? |
Looks like our Binder is back in business! You should go ahead and merge if you're happy with the changes. |
It looks like the merge to main workflow is failing because python 3.12 is being used somewhere. The notebook environment specifies python <= 3.11 to avoid python 3.12. But it must still be used somewhere in the build actions. |
Ugh. I think this is another bug in our workflows. Looks like the Binder is being pointed to the wrong branch and picking up the wrong environment file. I'll try manually triggering a new publish workflow. |
Ok, so the manual publish run seemed to work fine: https://github.com/ProjectPythia/na-cordex-viz-cookbook/actions/runs/7294855106 You should be all set. I think there are still a number of bugs in our workflow logic for handling changes in the environment files. Things are simpler for PRs that don't modify |
Fixes #12
We are seeing an error with python 3.12.
The error comes from the intake-esm library.
This should resolve eventually as python 3.12 matures. See this post: pypa/pip#11501