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
Upgraded from v24.2.0 to v24.4.0 and exception logging started raising its own exceptions. Previously, the repr-error text would be used; therefore, rich.pretty.traverse() is hitting the same error as the previous logic and letting the exception leak. It isn't clear to me if Rich should be catching these or structlog (or if we just shouldn't have a few classes that cause this...) but I think it is unexpected for exception logging to start raising itself.
The text was updated successfully, but these errors were encountered:
Upgraded from v24.2.0 to v24.4.0 and exception logging started raising its own exceptions. Previously, the
repr-error
text would be used; therefore,rich.pretty.traverse()
is hitting the same error as the previous logic and letting the exception leak. It isn't clear to me if Rich should be catching these or structlog (or if we just shouldn't have a few classes that cause this...) but I think it is unexpected for exception logging to start raising itself.The text was updated successfully, but these errors were encountered: