labextension install fails when read-only template yarn.lock is copied into staging directory #7525
Labels
bug
status:resolved-locked
Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Milestone
Description
jupyter labextension install myextension --app-dir=./myapp
fails with
when the template
yarn.lock
file that is included in the base jupyterlab package is readonly. In this case, it seems to be copied over to./myapp
when the staging directory is populated without setting the appropriate access rights:jupyterlab/jupyterlab/commands.py
Line 1181 in 172e664
This naturally occurs when installing jupyterlab with Nix, where the base install has to be immutable to ensure reproducibility. A simple fix would be to set write access on the copied
yarn.lock
in the staging directory.Reproduce
(I can only give approximate steps for a standard conda or pip install because I am using nix to install jupyterlab)
staging
directory.chmod -w yarn.lock
inside of the staging directoryjupyter labextension install <<anyextension>> --app-dir=. --debug
Expected behavior
Jupyterlab with the extension is built successfully in
app-dir
.Context
The text was updated successfully, but these errors were encountered: