You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey and thank you for this cool project :) I've recently caught this error on our CI. It seems like a one-off failure or at least I don't know how to reproduce it, but wanted to report it.
console.log div contained:
wasm-bindgen: imported JS function that was not marked as `catch` threw an error:
Cannot perform Construct on a detached ArrayBuffer
Stack:
TypeError: Cannot perform Construct on a detached ArrayBuffer
at new Uint8Array (<anonymous>)
at http://127.0.0.1:45979/wasm-bindgen-test:821:21
at logError (http://127.0.0.1:45979/wasm-bindgen-test:15:18)
at imports.wbg.__wbg_new_a12002a7f91c75be (http://127.0.0.1:45979/wasm-bindgen-test:820:66)
at tonic-0a60b64dc0c378db.wasm.__wbg_new_a12002a7f91c75be externref shim (http://127.0.0.1:45979/wasm-bindgen-test_bg.wasm:wasm-function[11739]:0x3d8547)
at tonic-0a60b64dc0c378db.wasm.js_sys::Uint8Array::new::hd19c385c5c06e79c (http://127.0.0.1:45979/wasm-bindgen-test_bg.wasm:wasm-function[6907]:0x393fcd)
at tonic-0a60b64dc0c378db.wasm.<js_sys::Uint8Array as core::convert::From<&[u8]>>::from::hef436ecde67c2879 (http://127.0.0.1:45979/wasm-bindgen-test_bg.wasm:wasm-function[6249]:0x3829b3)
at tonic-0a60b64dc0c378db.wasm.tonic_web_wasm_client::call::prepare_body::{{closure}}::{{closure}}::h3ef7b83f9a746715 (http://127.0.0.1:45979/wasm-bindgen-test_bg.wasm:wasm-function[6865]:0x392eda)
at tonic-0a60b64dc0c378db.wasm.core::option::Option<T>::map::h1480b2b09967572e (http://127.0.0.1:45979/wasm-bindgen-test_bg.wasm:wasm-function[3005]:0x2f3d70)
at tonic-0a60b64dc0c378db.wasm.tonic_web_wasm_client::call::prepare_body::{{closure}}::h60cd4ae367056104 (http://127.0.0.1:45979/wasm-bindgen-test_bg.wasm:wasm-function[846]:0x1e11ef)
The text was updated successfully, but these errors were encountered:
Hey and thank you for this cool project :) I've recently caught this error on our CI. It seems like a one-off failure or at least I don't know how to reproduce it, but wanted to report it.
The text was updated successfully, but these errors were encountered: