Skip to content
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

Developer-friendly error reporting #192

Open
crazyboycjr opened this issue Sep 21, 2022 · 0 comments
Open

Developer-friendly error reporting #192

crazyboycjr opened this issue Sep 21, 2022 · 0 comments
Labels
misc Miscellaneous things

Comments

@crazyboycjr
Copy link
Contributor

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/

@crazyboycjr crazyboycjr added this to the Big Refactoring milestone Sep 21, 2022
@crazyboycjr crazyboycjr added the misc Miscellaneous things label Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
misc Miscellaneous things
Projects
None yet
Development

No branches or pull requests

1 participant