You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@toree.apache.org by "Ventsislav Konakchiyski (Jira)" <ji...@apache.org> on 2020/10/15 16:35:00 UTC
[jira] [Created] (TOREE-522) Release 0.4.0 changes around handling
iopub.error have broken error reporting in Jupyter Notebook UI
Ventsislav Konakchiyski created TOREE-522:
---------------------------------------------
Summary: Release 0.4.0 changes around handling iopub.error have broken error reporting in Jupyter Notebook UI
Key: TOREE-522
URL: https://issues.apache.org/jira/browse/TOREE-522
Project: TOREE
Issue Type: Bug
Components: Kernel
Affects Versions: 0.4.0
Environment: Both Spark 2.4.x and 2.2.x
The version of the notebook server is: 6.0.3
The server is running on this version of Python:
Python 3.7.6 (default, Jan 8 2020, 19:59:22)
[GCC 7.3.0]
Current Kernel Information:
Apache Toree
Reporter: Ventsislav Konakchiyski
Attachments: f12-toree-channels-api.png, notebook-versions.png
We have noticed that since the python package was released, all of our images that were build after 0.4.0 was released were not reporting errors in the notebook UI when running broken code.
What happens:
1. Open a Toree - Scala notebook
2. Type some random broken code
3. As far as the UI is concerned, it has ran successfully and no error was reported to the user.
Inspecting the network requests, I can see that the error does come back from the API, but the UI is not handling it correctly. See screenshot f12-toree-channels-api.png
Reverting back to 0.3.0 release works fine as per notebook-versions.png screenshot
Let me know if you need more details
--
This message was sent by Atlassian Jira
(v8.3.4#803005)