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

JupyterLab is broken in new Foundations environment #486

Closed
brian-rose opened this issue Jul 22, 2024 · 0 comments · Fixed by #487
Closed

JupyterLab is broken in new Foundations environment #486

brian-rose opened this issue Jul 22, 2024 · 0 comments · Fixed by #487
Labels
infrastructure Infrastructure related issue

Comments

@brian-rose
Copy link
Member

As discussed in #485, our instructions for local environment creation are out of date. I'll open a PR to resolve #485 shortly.

However I've discovered that after creating a fresh version of the pythia-book-dev environment, JupyterBook will not launch. Running jupyter lab produces

Traceback (most recent call last):
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/bin/jupyter-lab", line 6, in <module>
    from jupyterlab.labapp import main
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyterlab/__init__.py", line 8, in <module>
    from .handlers.announcements import (
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyterlab/handlers/announcements.py", line 15, in <module>
    from jupyterlab_server.translation_utils import translator
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyterlab_server/__init__.py", line 6, in <module>
    from .app import LabServerApp
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyterlab_server/app.py", line 10, in <module>
    from jupyter_server.extension.application import ExtensionApp, ExtensionAppJinjaMixin
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyter_server/extension/application.py", line 17, in <module>
    from jupyter_server.serverapp import ServerApp
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyter_server/serverapp.py", line 39, in <module>
    from jupyter_events.logger import EventLogger
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyter_events/__init__.py", line 3, in <module>
    from .logger import EVENTS_METADATA_VERSION, EventLogger
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyter_events/logger.py", line 19, in <module>
    from .schema import SchemaType
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyter_events/schema.py", line 18, in <module>
    from .validators import draft7_format_checker, validate_schema
  File "/Users/br546577/miniconda3/envs/pythia-book-dev/lib/python3.12/site-packages/jupyter_events/validators.py", line 44, in <module>
    JUPYTER_EVENTS_SCHEMA_VALIDATOR = Draft7Validator(
                                      ^^^^^^^^^^^^^^^^
TypeError: create.<locals>.Validator.__init__() got an unexpected keyword argument 'registry'

This is on a Mac laptop (osx-arm64).

The problem appears to be upstream in jupyter_events, and has been reported in jupyter/jupyter_events#99.

I'm not sure if the problem is isolated to osx-arm64 or not. This is not something that our CI testing will catch, since we don't launch JupyterLab in those tests.

Pinning to Python < 3.12 resolves the problem.

I will open a PR for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Infrastructure related issue
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant