[
https://issues.apache.org/jira/browse/TOREE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luciano Resende resolved TOREE-522.
-----------------------------------
Fix Version/s: Not Applicable
Resolution: Resolved
As [~kbates] mentioned, this is an issue on Jupyter Notebook and should be
resolved on future release.
> 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
> Assignee: Luciano Resende
> Priority: Critical
> Fix For: Not Applicable
>
> Attachments: f12-toree-channels-api.png,
> jupyter-classic-behavior.png, jupyterlab-behavior.png,
> notebook-no-error-0.4.0.png, notebook-versions.png, screenshot-1.png,
> toree-current-lab.png, toree-current-nb-w-traceback.png, toree-fix-nb.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.
> See screenshot `notebook-no-error-0.4.0.png`
>
> 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.20.10#820010)
