You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we have noticed that when python raises an exception within a solara component, the error is shown in the browser, but not propagated back to the server.
This means that when looking at the server log, we are unaware of any problems our users might have. Instead, the user is confronted with the exception.
This behavior differs from usual python behavior and was unexpected for us.
The obvious (and cumbersome) solution would be to wrap every single python function and catch and log errors, before the exception is swallowed by the component.
Is there a recommended way to force components to log errors and or propagate them to their parent, or do you have other ideas how to achieve this?
Thank you for your work!
The text was updated successfully, but these errors were encountered:
Hi,
we have noticed that when python raises an exception within a solara component, the error is shown in the browser, but not propagated back to the server.
This means that when looking at the server log, we are unaware of any problems our users might have. Instead, the user is confronted with the exception.
This behavior differs from usual python behavior and was unexpected for us.
The obvious (and cumbersome) solution would be to wrap every single python function and catch and log errors, before the exception is swallowed by the component.
Is there a recommended way to force components to log errors and or propagate them to their parent, or do you have other ideas how to achieve this?
Thank you for your work!
The text was updated successfully, but these errors were encountered: