executablebooks/thebewhere we currently have a CSS issue. Specifically the library imports "@jupyterlab/rendermime/style/index.css" in order to support correct rendering of cell outputs. This is causing issues, as importing this file in turn imports
https://github.com/jupyterlab/jupyterlab/blob/master/packages/ui-components/style/base.csswhich contains css that affects high level selectors
aetc... this is causing issues for downstream users of the lib. That file is subsequently imported into many other jupyterlab packages via
jupyterlab/packages/cells/style/index.cssso those rules are duplicated. In any case that makes it difficult for a library like thebe to consume select packages from
jupyterlabI wondered if anyone here was familiar with or had thoughts on this?
Release day! I'll start 3.1.x once jupyterlab/jupyterlab#11028 is in
and the first RetroLab release fully done with the Jupyter Releaser! https://github.com/jupyterlab/retrolab/releases/tag/v0.3.5
We have disabled check xsrf here, but even then running
jupyter lab --config jupyter_server_test_config.py is logging
[W 2021-09-09 10:16:17.003 ServerApp] 403 PUT /api/contents/test-jupyterlab-menus-Close-all-menus-jupyterlab-retry1 (127.0.0.1): '_xsrf' argument missing from POST
[W 2021-09-09 10:16:17.003 ServerApp] '_xsrf' argument missing from POST
Benchmark reporting is working: https://github.com/jupyterlab/jupyterlab/pull/11052#issuecomment-916778330
It will probably requires some improvement to be less invasive (I'm thinking of using details element). But the bad news is that the test machines are not homogeneous.
jupyterlab-latexhere? Could somebody take a look at my PR here: jupyterlab/jupyterlab-latex#171 It's been reviewed earlier and should be ready to merge, but I'm ready to address comments or issues if it is not ready