From: "Ludovic Courtès" <ludo@gnu.org>
To: Domagoj Stolfa <ds815@gmx.com>
Cc: 49355@debbugs.gnu.org
Subject: bug#49355: [guix-jupyter] timeout issue running the kernel
Date: Tue, 06 Jul 2021 17:48:55 +0200 [thread overview]
Message-ID: <87zguzphnc.fsf@gnu.org> (raw)
In-Reply-To: <YOOyi0jCB3naP8R8@pepehands> (Domagoj Stolfa's message of "Tue, 6 Jul 2021 02:31:55 +0100")
Hi,
Domagoj Stolfa <ds815@gmx.com> skribis:
> After a very painful bisect with various issues appearing in jupyter (unrelated
> to this one), I've identified the first good commit and the first bad commit.
>
> The commit range which caused the problem is between
>
> 95f25c9b13e22603c35f3acd9048fbd1c8671925
>
> and
>
> 9e7f09cbec40257619e57edfdd700c775e96833d
>
> which is a series of commits by Ricardo updating a bunch of python stuff,
> including jupyter. My suspicion is that the update to jupyter-core from 4.4.0 to
> 4.7.1 (2a12cbaaab970bcab09002e952e062da0274f0b6) caused jupyter-core to no
> longer agree with the guix kernel. I haven't diagnosed further.
>
> The first good commit is 85788dd64d5c54ff52f19c8bb6c8c522ed581b2c and the first
> bad commit I was able to actually get jupyter to work on is
> 9e7f09cbec40257619e57edfdd700c775e96833d.
Thanks for bisecting!
I believe this is fixed by
<https://gitlab.inria.fr/guix-hpc/guix-kernel/-/commit/bc81615c11b67abe6533d7e076cf152d06618866>.
You should be able to try it out by running:
guix environment --ad-hoc jupyter guix-jupyter \
--with-branch=guix-jupyter=master -- \
jupyter notebook --debug --no-browser
Hmm now that I re-test it seems to be unreliable. Perhaps I’m missing
something else.
Let me know if it works for you!
Ludo’.
next prev parent reply other threads:[~2021-07-06 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 15:30 bug#49355: [guix-jupyter] timeout issue running the kernel Domagoj Stolfa
2021-07-05 20:54 ` Domagoj Stolfa
2021-07-06 1:31 ` Domagoj Stolfa
2021-07-06 15:48 ` Ludovic Courtès [this message]
2021-07-06 16:12 ` Domagoj Stolfa
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=87zguzphnc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=49355@debbugs.gnu.org \
--cc=ds815@gmx.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.