ipython / ipython/ipykernel

errors not reported in new async code

Offen
#1,279 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
Python
Sterne
734
Forks
412
Ø Merge
1 T. 5 Std.
Gemergte PRs (30 T.)
8

Beschreibung

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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.