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

No-panic check tracking issue #516

Open
14 of 20 tasks
newpavlov opened this issue Oct 14, 2024 · 0 comments
Open
14 of 20 tasks

No-panic check tracking issue #516

newpavlov opened this issue Oct 14, 2024 · 0 comments
Labels
help wanted Extra attention is needed testing

Comments

@newpavlov
Copy link
Member

newpavlov commented Oct 14, 2024

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 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed testing
Projects
None yet
Development

No branches or pull requests

1 participant