-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Exception is not properly detected in Databricks #2455
Comments
The workaround is to save ip = get_ipython()
ip__showtraceback = ip._showtraceback
rich.traceback.install(...)
ip._showtraceback = ip__showtraceback The workaround is crucial for me because a dependency is installing ip = get_ipython()
ip__showtraceback = ip._showtraceback
from kedro.framework.startup import bootstrap_project
ip._showtraceback = ip__showtraceback |
I'm a maintainer of Kedro 🙂 We have a PR that would disable the If this can't be fixed on the rich side then we can merge that, but if it is possible to get exception handling working correctly on Databricks that would be even better 🙏 |
One for the Kendro maintainers. |
I hope we solved your problem. If you like using Rich, you might also enjoy Textual |
If
rich.traceback
is installed (e.g., by a package like Kedro), the traceback of the error is, and string output for the cell in Databricks notebook, and the run is not interrupted.The installed package (Kedro) used in our solution use
rich.traceback
. Therefore, putting the solution into production is impossible because the orchestration tool does not get an error output from the Databricks.Zaznam.obrazovky.2022-08-03.v.14.44.57.mov
Platform
Click to expand
Azure Databricks single node cluster
Report output:
The text was updated successfully, but these errors were encountered: