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

jupyterhub - the sequel #31950

Closed
wants to merge 3 commits into from
Closed

jupyterhub - the sequel #31950

wants to merge 3 commits into from

Conversation

cstrahan
Copy link
Contributor

Motivation for this change

@ixxie got jupyterhub 99% packaged in #31871; this just puts the finishing touches in place.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

Copy link
Member

@disassembler disassembler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the contribution. Just a couple of suggestions. Also, should we have a nixos service added as well?

@@ -10042,6 +10048,8 @@ in {

jupyter_core = callPackage ../development/python-modules/jupyter_core { };

jupyterhub = callPackage ../development/python-modules/jupyterhub { };
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this should be in pythonPackages (or python-modules). Since it provides a binary to run, I think this should be a separate application in top-level

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes and no, its a bit tricky. The jupyterhub and the notebook are applications, and could/should be outside of python-packages.nix, but notebook needs a kernel and that one needs to be inside python-packages.nix. Doing it that way requires a bit more setup to get e.g. a Python 3 kernel with a Python 2 notebook, so this is a more pragmatic solution. In the long-term I think we should go in that direction, providing a function that allows you to add kernels to your notebook.

traitlets
];

# Disable tests because they take an excessive amount of time to complete.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How long is an excessive amount of time?

Copy link
Contributor Author

@cstrahan cstrahan Nov 24, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I let it run for about 20 minutes. The build logs showed that some routes were being hit, so presumably the tests were running (because what else could be making requests within the build environment?). At 20 minutes in, and with a mere 5 or 6 lines of "GET / [... blah ...]" in the build log, I gave up on waiting. I don't know what the tests were doing, but they seemed to be doing it a glacial pace.

@ixxie
Copy link
Contributor

ixxie commented Dec 3, 2017

@disassembler - are the changes in your review still requested or do you agree with @FRidh?

@orivej
Copy link
Contributor

orivej commented Dec 9, 2017

This PR has to resolve conflicts with the master branch.

@ixxie
Copy link
Contributor

ixxie commented Dec 25, 2017

@disassembler, @FRidh, @orivej - I merged this PR back into mine (#31871) and made the requested changes.

@aborsu
Copy link
Contributor

aborsu commented Jan 21, 2018

#31871 was merged and took the changes from this one so this PR can be closed

@FRidh FRidh closed this Jan 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants