-
Notifications
You must be signed in to change notification settings - Fork 953
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
Implement missing PrettyError impls #3066
Conversation
I notice that these are possibly missing label formatting:
|
I also promote this to a point release if merged :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the nick of time; changelog pls!
@scoopr thank you so much for going after this! But wasn't the bug I encountered a missing pretty print for |
(if closing the bug was not intended, that is my fault not scoopr's - I edited the body to close) |
yeah from my understanding the issue is still there, but scoopr's changes are great regardless :) |
Reopened! |
This should fix #3061, I believe I misattributed the missing bits initially, when talking about it on Matrix. The #3061 error that is missing label is actually Neither It would be great if you tested with the original error condition though, to make sure! |
ohhh I see that makes sense, double missunderstanding then :). I'll test it today and get back to you! |
confirmed fixed and suspecting that this was working already: the error I had was
As you can see it prints the encoder name but not the render pipeline name. So turns out I was in release mode the whole time, in debug in prints render pipeline label just fine. Encoder prints its name regardless because it is today the only resource that will still remember its name even if debug assertions are disabled (it has an overwrite here https://github.com/gfx-rs/wgpu/blob/master/wgpu-core/src/command/mod.rs#L237) Took me an awful long time to realize that, but well I learned quite a bit in the process I'd like to believe :) |
the fact that encoders keep their label regardless of debug_assertions enabled could be regardless a bug - but it seems it makes the code a lot easier since it needs to pass on that label to commandbuffer, so the tradeoffs are imho in favor of status quo |
Oh alright, that makes more sense, |
Checklist
cargo clippy
.RUSTFLAGS=--cfg=web_sys_unstable_apis cargo clippy --target wasm32-unknown-unknown
if applicable.Connections
Closes #3061
Description
Some of the Error impls that refer to the resource ids were not formatting the labels for the resources
Testing
I must confess that I only compile-tested. Inducing or synthesizing the error conditions are a bit difficult.