Skip to content
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

Make a release to work with JupyterHub 3+ #277

Closed
consideRatio opened this issue Jun 19, 2023 · 12 comments · Fixed by #302
Closed

Make a release to work with JupyterHub 3+ #277

consideRatio opened this issue Jun 19, 2023 · 12 comments · Fixed by #302

Comments

@consideRatio
Copy link
Member

consideRatio commented Jun 19, 2023

It seems we need to get a release out (newer than 1.2.0) to work with JupyterHub 3+, which work currently but not in the latest 1.2.0 release.

@mehalter
Copy link

I can also confirm that it seems to be working on main and looking forward to a new release to be able to update JupyterHub on a production cluster! Thanks so much for your hard work here 🥳

@FilipeMaia
Copy link

I would urge a quick new release. Having a hard-to-debug failure with the currently released version, when the fix is already merged for several months is not a good experience.

@krokicki
Copy link
Contributor

I just spent four extremely frustrating hours trying to debug this. After finally giving up, I came to log an issue here and stumbled upon this. If the release isn't imminent, and it doesn't seem to be, please consider updating the README to reflect the fact that you have to install from the repo for the time being.

I made PR #290 for adding this warning to the README, to save others the trouble I just went through.

@leosala
Copy link

leosala commented Nov 23, 2023

having an updated release would be very useful, we rely on this for multiple Hub instances. @mbmilligan any chance to have this in the next future? How can we help?

@basnijholt
Copy link

Any reason to postpone making a release?

Ran into an issue as well, until I realized one needs to install the latest main branch.

@aktech
Copy link

aktech commented Feb 20, 2024

@consideRatio @mbmilligan @rkdarst Is there anything I can do to help with the release? We use batchspawner for https://github.com/nebari-dev/nebari-slurm

@consideRatio
Copy link
Member Author

Only @mbmilligan has credentials to push a release to PyPI =/

@mbmilligan this could be addressed by #269

@basnijholt
Copy link

@mbmilligan could you add the other maintainers to PyPI?

If there is no activity soon I might fork and publish under batchspawner2 (but rather not 🥲).

@JacobJanzen
Copy link

I'm also relying on batchspawner for a project I'm working on and ran into problems when upgrading JupyterHub. Is there any timeline for when we could expect a new release @mbmilligan?

@basnijholt
Copy link

@consideRatio perhaps you can make a tag and we can just release batchspawner on conda-forge?

@basnijholt
Copy link

Awesome! Did you get the rights to publish to PyPI?

@Avatat
Copy link

Avatat commented Apr 2, 2024

@basnijholt I can see the new release in PyPI as well :)

Thank you all for the findings and the new release working with the latest JupyterHub!
I was able to run JH 4.1.5 on a Slurm queue successfully!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants