Sergey "Shnatsel" Davidoff

FWIW this is strictly required for Memory Sanitizer to work. Right now enabling msan in cargo-fuzz makes any binary immediately abort with a MSAN error. This is documented in more...

This is now as simple as `cargo fuzz run target_name -Z build-std` Also, #233 automatically enables this option if Memory Sanitizer is enabled.

According to [this Mozilla blog post](https://hacks.mozilla.org/2021/04/eliminating-data-races-in-firefox-a-technical-report/), Thread Sanitizer will not detect some of the races unless `-Z build-std` is used. I assume this also applies to Address Sanitizer, since some...

Also `svgparser`, `cpp_demangle`, `pulldown-cmark`

**TL;DR:** The non-standard field causes issues for anyone trying to produce or consume OSV data. Please prioritize the migration to the `last_affected` field from OSV 1.3. Right now GHSA data...

Is re-generation of the existing files planned? It's great that the new files are not affected, but the existing ones still cause false positives when parsed according to the OSV...

> I believe the Rust advisory database only reports crates vulnerabilities in OSV format. Yes, that is correct. > Should we also export the toolchain vulnerabilities (and use a separate...

I have also received a report of the same error in my project when run in Mac OS 10.14.6: `Could not load platform certs: "The Trust Settings Record was corrupted."`...

There is a design and a good chunk of a Rust implementation for a concurrent hash table based on nested hash tables, so that reallocation would not block all threads:...

Memory allocations and thread spawning are not the bottlenecks in jpeg-decoder. Spawning threads is really cheap (my mid-range desktop can spawn 50,000 of them a second) and reducing the amount...