-
Notifications
You must be signed in to change notification settings - Fork 45
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
Tracking issue: synchronous exceptions in JS API #225
Labels
errors
Error reporting
has resolution
Issue is resolved, just needs to be done
wasm
Issues with WebAssembly targets
Comments
Note this is in addition to synchronous errors from the C API that don't exist in the JS API (like #115). |
Dec 14 meeting:
|
Marking "has resolution", we can figure out #232 when we get to it |
kainino0x
added a commit
to kainino0x/webgpu-headers
that referenced
this issue
Oct 19, 2024
Fixes webgpu-native#255 Fixes (again?) webgpu-native#291 Issue webgpu-native#225
kainino0x
added a commit
to kainino0x/webgpu-headers
that referenced
this issue
Oct 19, 2024
Fixes webgpu-native#255 Fixes (again?) webgpu-native#291 Issue webgpu-native#225 Fixes webgpu-native#64
kainino0x
added a commit
to kainino0x/webgpu-headers
that referenced
this issue
Oct 19, 2024
Fixes webgpu-native#255 Fixes (again?) webgpu-native#291 Issue webgpu-native#225 Fixes webgpu-native#64
kainino0x
added a commit
to kainino0x/webgpu-headers
that referenced
this issue
Oct 19, 2024
Fixes webgpu-native#255 Fixes (again?) webgpu-native#291 Issue webgpu-native#225 Fixes webgpu-native#64
One new addition:
|
I handled that in #377 by making it also a device error in webgpu.h (same as for formats not supported by the surface, and formats not supported by the device) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
errors
Error reporting
has resolution
Issue is resolved, just needs to be done
wasm
Issues with WebAssembly targets
I'll attempt to make a complete list of entrypoints that have synchronous exceptions in the JS API:
mapAtCreation==true
#57)One approach we've been taking for some entrypoints is to say "return a generic error code, with implementation-defined logging" (eventually we're likely to make it well-defined, with a log callback on the instance):
The text was updated successfully, but these errors were encountered: