William Woodruff

Taking a look about two years later: it looks like this isn't currently supported. I could take a stab at implementing it, if nobody else is currently trying.

Looks like `rusb`, which is the actively maintained fork of this crate, already has hotplug support: https://docs.rs/rusb/0.6.5/rusb/trait.UsbContext.html#method.register_callback

I've experienced the same error (platform: Ubuntu 18.04, x86_64), with: ```bash $ valgrind --version valgrind-3.13.0 ``` My `callgrind.out`: [callgrind.out.txt](https://github.com/svenstaro/cargo-profiler/files/4639192/callgrind.out.txt)

For `pip-audit` users, you can temporarily ignore this disputed vulnerability using the `--ignore-vuln` flag: ```console $ pip-audit --ignore-vuln GHSA-rwqr-c348-m5wr ```

My understanding is that it was a process breakdown: someone directly reported a "crash" they found with OSS-fuzz and got it accepted by one of the CVE assigning authorities, rather...

> Not me, I gave up on that after having filled out the forms per their processes. They are ghosting me (and I assume others too?) + there's no alternative...

> I believe that's exactly what me and the others did too. Ah, dang. In that case I'm probably retracing your exact steps 😅; sorry for the confusion.

`pip-audit` maintainer here: once the advisory is purged from GHSA and other DBs, `pip-audit` should stop displaying it. I'm coordinating with the PYSEC database maintainers now to ensure that we...

No problem, many thanks to @alex for bringing it to my attention! I've posted a temporary "workaround" for `pip-audit` users here: https://github.com/aio-libs/aiohttp/issues/6772#issuecomment-1167464922

`pip-audit` is also no longer reporting this: ```console pip-audit --no-deps -r