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
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
I was encountering an issue with their tracing example, cause I had other error handlers initiated. This helped me, since I wanted to only enable the panic hook but not the error hook. Same principle above, except .0 instead of .1. Thanks!
Edit: Figured out the issue, for some reason using eyre (eyre!() and Result) before setting the hooks somehow caused a hook to get set, even though I never set it. That caused the error hook to error out as it was already "set"
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add an option for the builder to disable the setting the panic hook, and only setting the eyre hook.
This is useful for targeting the web where you may already use
console_error_panic_hook
The text was updated successfully, but these errors were encountered: