Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #9973 > unrolled thread
| Started by | Andreas Tille <andreas@an3as.eu> |
|---|---|
| First post | 2017-11-09 15:40 +0100 |
| Last post | 2017-11-12 22:20 +0100 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.debian.maint.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#880245: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)] Andreas Tille <andreas@an3as.eu> - 2017-11-09 15:40 +0100
Re: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)] Gordon Ball <gordon@chronitis.net> - 2017-11-09 20:50 +0100
Re: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)] Andreas Tille <andreas@an3as.eu> - 2017-11-10 17:30 +0100
Re: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)] Gordon Ball <gordon@chronitis.net> - 2017-11-12 22:20 +0100
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2017-11-09 15:40 +0100 |
| Subject | Bug#880245: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)] |
| Message-ID | <uJW09-6pt-11@gated-at.bofh.it> |
Hi,
statsmodels upstream claims that #880245 is a ipython/jupyter issue.
Is there anybody with some knowledge and knows how to fix this issue?
Kind regards
Andreas.
----- Forwarded message from Josef Perktold <notifications@github.com> -----
Date: Thu, 09 Nov 2017 12:51:38 +0000 (UTC)
From: Josef Perktold <notifications@github.com>
To: statsmodels/statsmodels <statsmodels@noreply.github.com>
Cc: Andreas Tille <tille@debian.org>, Author <author@noreply.github.com>
Subject: Re: [statsmodels/statsmodels] RuntimeError: Kernel died before replying to kernel_info (#4116)
This is a ipython/jupyter issue, and not related to statsmodels. You can ask at their issue tracker.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/statsmodels/statsmodels/issues/4116#issuecomment-343145298
----- End forwarded message -----
--
http://fam-tille.de
[toc] | [next] | [standalone]
| From | Gordon Ball <gordon@chronitis.net> |
|---|---|
| Date | 2017-11-09 20:50 +0100 |
| Subject | Re: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)] |
| Message-ID | <uK0ZP-1a9-11@gated-at.bofh.it> |
| In reply to | #9973 |
On 09/11/17 15:27, Andreas Tille wrote:
> Hi,
>
> statsmodels upstream claims that #880245 is a ipython/jupyter issue.
>
> Is there anybody with some knowledge and knows how to fix this issue?
I just built statsmodels 0.8.0-6 in and amd64 sbuild chroot without
encountering this issue.
Looking at the trace in #880245, it looks like the key error is
zmq.error.ZMQError: Address already in use
and the other
RuntimeError: Kernel died before replying to kernel_info
are just caused by the other process not being able to communicate. My
guess is that this is an environment heisenbug - container network
issues/socket exhaustion...
It might be possible to get `ExecutePreprocessor` in
`tools/nbgenerate.py` to use IPC instead of TCP transport, which might
be more reliable for this sort of use (although it probably doesn't get
tested as much, so might have its own problems); this is a supported
option when invoking some CLI tools (eg, `jupyter console --transport
ipc --kernel python3`), but it's not obvious to me how to do it in this
case.
Gordon
>
> Kind regards
>
> Andreas.
>
> ----- Forwarded message from Josef Perktold <notifications@github.com> -----
>
> Date: Thu, 09 Nov 2017 12:51:38 +0000 (UTC)
> From: Josef Perktold <notifications@github.com>
> To: statsmodels/statsmodels <statsmodels@noreply.github.com>
> Cc: Andreas Tille <tille@debian.org>, Author <author@noreply.github.com>
> Subject: Re: [statsmodels/statsmodels] RuntimeError: Kernel died before replying to kernel_info (#4116)
>
> This is a ipython/jupyter issue, and not related to statsmodels. You can ask at their issue tracker.
>
[toc] | [prev] | [next] | [standalone]
| From | Andreas Tille <andreas@an3as.eu> |
|---|---|
| Date | 2017-11-10 17:30 +0100 |
| Subject | Re: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)] |
| Message-ID | <uKklP-5LY-3@gated-at.bofh.it> |
| In reply to | #9974 |
Hi,
On Thu, Nov 09, 2017 at 08:48:02PM +0100, Gordon Ball wrote:
>
> I just built statsmodels 0.8.0-6 in and amd64 sbuild chroot without
> encountering this issue.
>
> Looking at the trace in #880245, it looks like the key error is
>
> zmq.error.ZMQError: Address already in use
>
> and the other
>
> RuntimeError: Kernel died before replying to kernel_info
>
> are just caused by the other process not being able to communicate. My
> guess is that this is an environment heisenbug - container network
> issues/socket exhaustion...
IMHO this would be a good reason to lower the severity of the bug, isn't
it?
> It might be possible to get `ExecutePreprocessor` in
> `tools/nbgenerate.py` to use IPC instead of TCP transport, which might
> be more reliable for this sort of use (although it probably doesn't get
> tested as much, so might have its own problems); this is a supported
> option when invoking some CLI tools (eg, `jupyter console --transport
> ipc --kernel python3`), but it's not obvious to me how to do it in this
> case.
Any further hits?
Kind regards
Andreas.
--
http://fam-tille.de
[toc] | [prev] | [next] | [standalone]
| From | Gordon Ball <gordon@chronitis.net> |
|---|---|
| Date | 2017-11-12 22:20 +0100 |
| Subject | Re: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)] |
| Message-ID | <uL7PA-5nU-11@gated-at.bofh.it> |
| In reply to | #9975 |
On 10/11/17 17:28, Andreas Tille wrote: > Hi, > > On Thu, Nov 09, 2017 at 08:48:02PM +0100, Gordon Ball wrote: >> >> I just built statsmodels 0.8.0-6 in and amd64 sbuild chroot without >> encountering this issue. >> >> Looking at the trace in #880245, it looks like the key error is >> >> zmq.error.ZMQError: Address already in use >> >> and the other >> >> RuntimeError: Kernel died before replying to kernel_info >> >> are just caused by the other process not being able to communicate. My >> guess is that this is an environment heisenbug - container network >> issues/socket exhaustion... > > IMHO this would be a good reason to lower the severity of the bug, isn't > it? You can check this for yourself, but yes - it appears that it does not consistently FTBFS, and therefore shouldn't be RC. > >> It might be possible to get `ExecutePreprocessor` in >> `tools/nbgenerate.py` to use IPC instead of TCP transport, which might >> be more reliable for this sort of use (although it probably doesn't get >> tested as much, so might have its own problems); this is a supported >> option when invoking some CLI tools (eg, `jupyter console --transport >> ipc --kernel python3`), but it's not obvious to me how to do it in this >> case. > > Any further hits? I don't think I have time to dig into this at the moment, but given the nbgenerate task is already run (docs/Makefile:58,70) with `--allow_errors=True` to ignore errors within the notebooks, I'd just patch the Makefile to ignore any errors from that command, which in the worst case will result in some documentation notebooks not being populated. > > Kind regards > > Andreas. >
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web