You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Noted on conda-forge/jupyter-collaboration-feedstock#12 (comment), the basic smoke test is failing for whether a user might see (or perceive) problems with their jupyterlab versions. Given the nature and complexity of this extension (and the changes in lab 4.1+), I would surprised if the 4.0.x versions in yarn.lockweren't masking some typescript-level issues. Indeed has been pinned, which is suspicious if not also provided as runtime constraints so users' package managers benefit from this wisdom in a meaningful way.
+ jupyter labextension list
JupyterLab v4.2.0
/home/conda/feedstock_root/build_artifacts/jupyter-collaboration_1715216099941/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/share/jupyter/labextensions
jupyterlab_pygments v0.3.0 enabled OK (python, jupyterlab_pygments)
@jupyter/collaboration-extension v2.1.1 enabled X (python, jupyter_collaboration)
The following extensions may be outdated or specify dependencies that are incompatible with the current version of jupyterlab:
@jupyter/collaboration-extension
If you are a user, check if an update is available for these packages.
If you are a developer, re-run with `--verbose` flag for more details.
Disabled extensions:
@jupyterlab/filebrowser-extension:defaultFileBrowser
"@jupyter/collaboration-extension@2.1.1" is not compatible with the current JupyterLab
Conflicting Dependencies:
JupyterLab Extension Package
>=2.0.1 <3.0.0 >=1.1.0-a0 <2.0.0 @jupyter/ydoc
Description
Noted on conda-forge/jupyter-collaboration-feedstock#12 (comment), the basic smoke test is failing for whether a user might see (or perceive) problems with their jupyterlab versions. Given the nature and complexity of this extension (and the changes in lab 4.1+), I would surprised if the
4.0.x
versions inyarn.lock
weren't masking some typescript-level issues. Indeed has been pinned, which is suspicious if not also provided as runtime constraints so users' package managers benefit from this wisdom in a meaningful way.Reproduce
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=930358&view=logs&j=656edd35-690f-5c53-9ba3-09c10d0bea97&t=986b1512-c876-5f92-0d81-ba851554a0a3&l=935
Expected behavior
Context
The text was updated successfully, but these errors were encountered: