ipython / ipython/ipykernel

errors not reported in new async code

Abierto
#1,279 0 comentarios 0 reacciones 0 asignados Ver en GitHub
bug
Lenguaje dominante
Python
Estrellas
734
Forks
412
Merge medio
1 d 5 h
PR fusionados (30 d)
8

Descripción

If errors are raised in the new async code, as I'm seeing in trying to update IPython Parallel to the new async APIs, there is often no indication of a problem, messages just don't get handled.

We need to be careful to catch and log all errors in ipykernel code, because the default excepthook sends them to the captured stderr stream, which won't be seen in the kernel logs. That means everything we launch with e.g. `start_soon` etc. must be hooked up to a generic try/except to catch and log all unhandled exceptions instead of letting them raise.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.