Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #9975

Re: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)]

Path csiph.com!feeder.erje.net!2.eu.feeder.erje.net!proxad.net!feeder1-2.proxad.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From Andreas Tille <andreas@an3as.eu>
Newsgroups linux.debian.maint.python, linux.debian.bugs.dist
Subject Re: ipython/jupyter issue [Was: RuntimeError: Kernel died before replying to kernel_info (#4116)]
Date Fri, 10 Nov 2017 17:30:01 +0100
Message-ID <uKklP-5LY-3@gated-at.bofh.it> (permalink)
References <uJW09-6pt-11@gated-at.bofh.it> <uK0ZP-1a9-11@gated-at.bofh.it>
X-Mailbox-Line From debian-python-request@lists.debian.org Fri Nov 10 16:28:50 2017
Old-Return-Path <andreas@an3as.eu>
X-Amavis-Spam-Status No, score=-6.901 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate: -6.1
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
User-Agent NeoMutt/20170113 (1.7.2)
X-Mailing-List <debian-python@lists.debian.org> archive/latest/15358
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/20171110162833.ng64vtq57us5c6x3@an3as.eu
Approved robomod@news.nic.it
Lines 38
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Fri, 10 Nov 2017 17:28:33 +0100
X-Original-Message-ID <20171110162833.ng64vtq57us5c6x3@an3as.eu>
X-Original-References <20171109142708.dzbxhiuqm4oi6xez@an3as.eu> <cb6987e8-9c4c-a2c2-b505-59faa582aa71@chronitis.net>
Xref csiph.com linux.debian.maint.python:9975 linux.debian.bugs.dist:862029

Cross-posted to 2 groups.

Show key headers only | View raw


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

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

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

csiph-web