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

Jupyter Extension Simultaneously Installed and Enabled But Not Working #15658

Closed
Padamire opened this issue Jan 18, 2024 · 4 comments
Closed
Labels
bug status:Needs Triage Applied to new issues that need triage

Comments

@Padamire
Copy link

Padamire commented Jan 18, 2024

Hey Guys

I've recently ran into an issue with a Jupyter Lab Extension (Jupyter Scheduler). I've tried installing it with 'mamba install', 'pip install' and through Pypi on the Lab Extension section, all of which require the simultaneous installation of croniter, pytz, fsspec and sqlachlemy. However, when that's complete, I get the following popup on Jupyter Lab.

image

I've followed the instructions, installing the server extension through either command prompt or anaconda prompt (which always states the requirement has already been satisified). A quick run of 'mamba list' shows that jupyter scheduler is installed at v 2.4.0. When I run Jupyter Server Extension List, I get the following output:

image

It shows that the extension is installed and enabled. The issue mimics a similar GitHub Issue: #8122. However, the main solution is to delete the build-config.json file in the settings folder of Jupyter Lab, but mine remains empty.

The only discrepancy I can think of is in Jupyter Labs Extension Manager, where Jupyter_Scheduler is shown both to be installed and not installed at the same time:
image
image
However, when I try to install the uninstalled version, I get a notification saying to refresh the page to apply the changes, but when I do that nothing happens.

I've run Jupyter Lab Build, updated Jupyter Lab to 4.0.8, tried every workaround but nothing seems to work.

I would really appreciate some help on this as I've already burned countless hours trying to fix it.

@Padamire Padamire added the bug label Jan 18, 2024
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to new issues that need triage label Jan 18, 2024
Copy link

welcome bot commented Jan 18, 2024

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@krassowski
Copy link
Member

@Padamire there are two separate extensions: jupyter-scheduler maintained within official jupyter-server organization and a third-party jupyterlab-scheduler. I do not know which one you intended to install, but probably not both. Beside this confusion your issue is most likely either (a) that the extension was installed in a different virtual environment or (b) that you need to restart jupyterlab for server to pickup the newly installed extension.

@Padamire
Copy link
Author

@krassowski I've restarted Jupyterlab multiple times (closing anaconda navigator, opening it again and launching the app) but I always get the same popup. I've even uninstalled and reinstalled Jupyterlab but got no results.

I checked which environment I was working in and it confirmed I was in the base environment

image

After running mamba list on that specific environment, it confirmed that jupyter_scheduler was installed.

image

image

So I'm not quite sure what the issue is. The only discrepancy I can note (if it is one at all) is that the scheduler extension always seems to be found in two separate directories:
image
Here it's found in the .jupyter folder.

image

and here it is in the anaconda3/etc/jupyter folder. This may just be normal practice but it may provide a clue to the issue at hand.

@JasonWeill
Copy link
Contributor

Let's keep the conversation going about this in jupyter-server/jupyter-scheduler#473, which you also opened. This seems to be an issue with installing Jupyter Scheduler, not in JupyterLab's handling of extensions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug status:Needs Triage Applied to new issues that need triage
Projects
None yet
Development

No branches or pull requests

3 participants