Michael Weinold

@12rambau, I checked further: Irregardless of the path I use for the `logo: image_light` variable: ``` source/_static/logo/logo_light.svg ./_static/logo/logo_light.svg logo/logo_light.svg ../../_build/html/_static/logo/logo_light.svg ``` the builder _always_ ends up looking for the file...

Just to be clear: _Uploading_ (ie. using this magic button): works just fine (for any file size). Reading the gzipped files (for instance, once they have been created with [the...

In both cases. I included the test function to show that the issue wasn’t my with my specific files.

Do you have any idea if this is an issue with JupyterLite, @jtpio?

The issue persists on ([complete requirements file](https://github.com/brightway-lca/brightway-live/blob/pyodide/requirements.txt)): ``` jupyterlite-core==0.3.0 jupyterlite-pyodide-kernel==0.3.1 ``` The only difference is that now I can not correctly create the successively larger tar-files. The files all remain...

I checked with the latest version of JupyterLite (0.4.0). Unfortunately, the issue persists: ```python ReadError: not a gzip file ```

I don't think this is related to https://github.com/jupyterlite/jupyterlite/issues/1047

Is there a way to check the utilized storage driver other than the visual browser console?

~~@jtpio, this worked for me:~~ > "settingsStorageDrivers": ["webSQLStorage"], > "contentsStorageDrivers": ["webSQLStorage"], ~~For instance, using the webSQLStorage content storage driver, I was able to use `sqlite3` without the error documented with...

...the original issue here was similarly resolved by fixing the config file json (removing trailing commas): https://github.com/jupyterlite/pyodide-kernel/issues/59