-
Notifications
You must be signed in to change notification settings - Fork 63
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
gcc fails when non-admin user tries to pip install a repo from within a notebook #144
Comments
I had another non-admin user try to run this notebook cell, and she didn't have the gcc failure, but did get the pip resolver warning, which unfortunately did then prevent the rest of the notebook from running so.... wtf is up with pip? Maybe this is only happening in this context because |
hmmmm I could see issues popping up with pip's new dependency solver if it is finding versions of things that were installed by a different tool...I wonder if @pradyunsg has run into this issue before? |
This was also resolved by #147. Catalyst Coop was accidentally on the pangeo image, rather than our own. The commands you provided worked for me now! Once we switch to your own docker image, these problems should go away. Re: admin / non-admin, I'm not sure why that would be :| |
@zaneselvans can you try it out and let me know if it works out ok? |
Hey @yuvipanda yes, it's working now! I'm still confused why the in-notebook software installs would have continued working for other users, but not for a new one -- maybe I'm misunderstanding how / when the Docker image is deployed. |
I sent a non-admin user a nbgitpuller link to our new tutorial notebook repo, to run on the Catalyst Cooperative pilot hub, the first cell of which installs the snappy compression library (using conda) and then our PUDL package. It also upgrades
pip
because I had previously gotten an error about the resolver not taking into account all installed packages, and wondered if a new version would address the issue. It appears that the pip upgrade worked, but the pip install of pudl from our repository resulted in a compiler error on the user's machine, pasted below.The error message I previously got from
pip
was:Testing now with fresh restarts of the server, I see that I get that error regardless of whether I upgrade pip, so I've removed that line from the first cell.
I haven't experienced the behavior below when running the same cell in the same notebook. Maybe it's because I'm an admin? Not sure what else would be different with a fresh slate after a new login.
notebook cell contents
resulting outputs
The text was updated successfully, but these errors were encountered: