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

handle_error_fatal does not print the complete error #3551

Closed
kpreid opened this issue Mar 2, 2023 · 0 comments · Fixed by #3563
Closed

handle_error_fatal does not print the complete error #3551

kpreid opened this issue Mar 2, 2023 · 0 comments · Fixed by #3563
Labels
help required We need community help to make this happen. type: bug Something isn't working

Comments

@kpreid
Copy link
Contributor

kpreid commented Mar 2, 2023

Description
I tried using a render bundle and got this error:

thread 'main' panicked at 'Error in RenderBundleEncoder::finish: In a set_pipeline command', /Users/kpreid/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.15.0/src/backend/direct.rs:316:9

Expected vs observed behavior
The error is incomplete: it doesn't say what was wrong with the operation. Based on the line number, this appears to be because

    fn handle_error_fatal(
        &self,
        cause: impl Error + Send + Sync + 'static,
        string: &'static str,
    ) -> ! {
        panic!("Error in {string}: {cause}");
    }

prints cause but not cause's chain (like non-fatal error handling does).

@teoxoy teoxoy added type: bug Something isn't working help required We need community help to make this happen. labels Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help required We need community help to make this happen. type: bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants