jupyterlab-contrib/jupyterlab-filesystem-access

Unstable reference from /drive in JupyterLite

Closed this issue · 5 comments

Description

Unstable reference from /drive in JupyterLite

  • Sometimes /drive refers to JupyterLite Storage
  • Sometimes /drive refers to Local Files (Certain bytes are incorrectly replaced to EFBFBD in this mode)

Is the Settings Storage setting in JupyterLite involved?
If it is related, please write it in the README.

Reproduce

detail drawio

Expected behavior

Some stable behavior

Context

  • JupyterLite version: 0.1.0-beta.17
  • jupyterlab-filesystem-access version: v0.5.3
  • Browser and its version: Chrome 108.0.5359.124 (Official Build) (x86_64)

There is no /drive in JupyterLab.
All file access is server-side.

Sometimes /drive is empty in the notebook in jupyterlab-filesystem-access.
In that case, reading /drive in the notebook in JupyterLite Storage will fix it.

It seems that the location of the notebook that reads /drive affects the behavior.

  • Notebook is directly in the top directory: /drive refers to JupyterLite Storage
  • Notebook is in some subdirectory: /drive refers to Local Files

This may be a bug in JupyterLite.
jupyterlite/issues/942

JupyterLite fixed