ASF GitHub Bot commented on TOREE-508:

gmcoringa commented on issue #180: [TOREE-508] Reply errors to iopub.error 
instead of iopub.exec_result
URL: https://github.com/apache/incubator-toree/pull/180#issuecomment-574800328
   > I believe we are going in the right direction here, but with the change on 
behavior the errors are not completely showing up on the notebook interface.
   > Original behavior:
   > And with the changes from this pr:
   > As shown in the picture above, the contents are not all there, and the 
cell is not scrollable anymore.
   The error is not completely showing because of the code below found in 
             formattedException.slice(1, formattedException.size - 1).toList
   Which removes the first line from the stack, I don't know why, but I believe 
that this should not be done.
   About the scrollable, testing with python kernels seems to have the same 
behaviour (errors are not scrollable).
   So @lresende if you think its better I can fix the removal of messages from 
the stack trace.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Reply errors to iopub.error instead of iopub.exec_result
> --------------------------------------------------------
>                 Key: TOREE-508
>                 URL: https://issues.apache.org/jira/browse/TOREE-508
>             Project: TOREE
>          Issue Type: Bug
>            Reporter: Fabiano V. Santos
>            Priority: Major
> Errors of any kind (compilation, exceptions, etc) returns as normal results 
> instead of using iopub.error, so jupyter interpret the cell execution as 
> success which lead to problems if you use tools like papermill to schedule 
> notebooks, as you never know if the notebook execution was successfully or 
> not.

This message was sent by Atlassian Jira

Reply via email to