I was experiencing some issues using the CLI (my fault). The error messages were produced unhelpful (such as Error: No such file or directory (os error 2), and I didn't know where the error was originating from.
Solution
To resolve this, I replaced anyhow with color_eyre as it improves upon anyhow in multiple ways. It not only improves the aesthetics of the error messages, but provides a much more useful stack trace, which pointed me to the issue in io.rs, so I improved the feedback of the error in io.rs, and this helped me identify the issue I was having.
Additionally, I added context messages to all ensure! macro calls in the integration tests to provide more context in the case of failures.
Motivation
I was experiencing some issues using the CLI (my fault). The error messages were produced unhelpful (such as
Error: No such file or directory (os error 2)
, and I didn't know where the error was originating from.Solution
To resolve this, I replaced
anyhow
withcolor_eyre
as it improves upon anyhow in multiple ways. It not only improves the aesthetics of the error messages, but provides a much more useful stack trace, which pointed me to the issue inio.rs
, so I improved the feedback of the error inio.rs
, and this helped me identify the issue I was having.Additionally, I added context messages to all
ensure!
macro calls in the integration tests to provide more context in the case of failures.