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
CI jobs responsible for no-panic checks are configures in nopanic.yaml. Ideally, we should check all our backends. Below is a list of existing backends divided into 3 categories.
use_file (checked implicitly via linux_android_with_fallback, would be nice to check explicitly)
wasi
windows7
windows
Unclear how to implement nopanic check:
esp_idf (direct call to esp_fill_random)
fuchsia (direct call to zx_cprng_draw)
vxworks
hermit
solid (direct call to SOLID_RNG_SampleRandomBytes)
No-panic check probably can not be implemented:
wasm_js: glue code generated by wasm-bindgen contains a lot of potential panics, so apparently it will not be possible to completely eliminate panics from generated file.
The text was updated successfully, but these errors were encountered:
CI jobs responsible for no-panic checks are configures in nopanic.yaml. Ideally, we should check all our backends. Below is a list of existing backends divided into 3 categories.
No-panic check can be implemented:
apple-other
custom
getentropy
getrandom
linux_android
linux_rustix
(depends on bytecodealliance/rustix#1184, should be released in rustix v0.38.38)linux_android_with_fallback
netbsd
rdrand
rndr
solaris
use_file
(checked implicitly via linux_android_with_fallback, would be nice to check explicitly)wasi
windows7
windows
Unclear how to implement nopanic check:
esp_idf
(direct call toesp_fill_random
)fuchsia
(direct call tozx_cprng_draw
)vxworks
hermit
solid
(direct call toSOLID_RNG_SampleRandomBytes
)No-panic check probably can not be implemented:
wasm_js
: glue code generated bywasm-bindgen
contains a lot of potential panics, so apparently it will not be possible to completely eliminate panics from generated file.The text was updated successfully, but these errors were encountered: