Cryptographically verifiable, distributed dependency reviews
Add the last reviewed version to Cargo.toml / [dependencies]:
wait-timeout = "0.2.0"Please, use mobile in landscape.
Filter reviews clicking on the numbers in the summary.
Full column names in tooltip hints: rating Negative, rating Neutral, rating Positive, rating Strong, thoroughness, understanding, reviews count.
The crate implements a seemingly trivial thing: waiting for a child process
to finish, with a timeout.
On Windows, this boils down to a single WinAPI call. I don't know much about
Windows, but the code looks okay to me. There is a minor issue of timeouts
being capped at ≈49 days, which I reported:
https://github.com/alexcrichton/wait-timeout/issues/23
On Unix, the algorithm is much more involved. I understand it, and I believe
it to be correct.
The crate calls into libc and WinAPI, so there are a bit of unsafe in here.
But it all looks all right to me.
© bestia.dev 2023, MIT License, Version: 2023.608.1636
Open source repository for this web app: https://github.com/bestia-dev/cargo_crev_web/
The crate implements a seemingly trivial thing: waiting for a child process
to finish, with a timeout.
On Windows, this boils down to a single WinAPI call. I don't know much about
Windows, but the code looks okay to me. There is a minor issue of timeouts
being capped at ≈49 days, which I reported:
https://github.com/alexcrichton/wait-timeout/issues/23
On Unix, the algorithm is much more involved. I understand it, and I believe
it to be correct.
The crate calls into libc and WinAPI, so there are a bit of
unsafein here.But it all looks all right to me.