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
Error reporting should at least print a stack trace so that the developer can quickly locate the direct source of the error.
Besides, there are several other issues around error reporting. E.g., a plugin initialization error currently reports nothing (probably it goes across some library boundary, but I'm not sure). For another example, we often run into folder permission denied or build-cache setting up errors.
Error reporting should at least print a stack trace so that the developer can quickly locate the direct source of the error.
Besides, there are several other issues around error reporting. E.g., a plugin initialization error currently reports nothing (probably it goes across some library boundary, but I'm not sure). For another example, we often run into folder permission denied or build-cache setting up errors.
Maybe combine thiserror and anyhow::Error since the latter collects the stack traces. Also, take a look at https://docs.rs/error-stack/latest/error_stack/
The text was updated successfully, but these errors were encountered: