Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] jupyterlab doesn't work out of the box
Date: Wed, 02 Feb 2022 21:25:30 +0100	[thread overview]
Message-ID: <20220202202530.OwUwONMejE5gje-IJCt541KSlXIA0r-5sRzpuMb8JHc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35341@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

Closed issue by tornaria on void-packages repository

https://github.com/void-linux/void-packages/issues/35341

Description:
### Steps to reproduce the behavior

1. install package `jupyterlab`
2. run `jupyter-lab` in a terminal (as a regular user fwiw)
3. an error pops up both in the terminal and in a browser:
```
[E 2022-02-01 09:38:05.353 LabApp] JupyterLab application assets not found in "/usr/share/jupyter/lab"
[E 2022-02-01 09:38:05.353 LabApp] Please run `jupyter lab build` or use a different app directory
```

I was able to workaround by creating my own app directory as follows:
```
$ mkdir ~/lab
$ jupyter lab build --app-dir=~/lab
```
and then run jupyter lab as
```
$ jupyter lab --app-dir=~/lab
```

Beware: this will take some time and bring up (download I guess?) ~400M of nodejs stuff. I'm not sure one would want to ship that inside the xbps, maybe give some warning or instructions to the user?

Cc: @dkwo

      parent reply	other threads:[~2022-02-02 20:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 12:53 [ISSUE] " tornaria
2022-02-01 13:56 ` dkwo
2022-02-01 14:03 ` dkwo
2022-02-01 14:43 ` tornaria
2022-02-01 16:27 ` dkwo
2022-02-01 16:54 ` ahesford
2022-02-02 10:12 ` dkwo
2022-02-02 20:25 ` ahesford [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220202202530.OwUwONMejE5gje-IJCt541KSlXIA0r-5sRzpuMb8JHc@z \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).