enricobuehlerandClaude Fable 5 ecb3d1ab22 fix(host/windows): the pad service thread no longer waits on pnputil at its leisure ...

driver_store_inventory() ran `pnputil /enum-drivers` synchronously inside
the attach-failure diagnose path — on the pad service thread, with no
timeout. A busy or wedged driver store blocks that enumeration for tens
of seconds, and the thread must keep draining pad slots.

The query now runs on its own thread (spawned once per process); the
caller waits a bounded 2 s so a fast pnputil still lands in the same
report, and a slower one fills the cache for later diagnoses — the WARN
then says the store could not be queried yet instead of blocking.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-30 23:35:32 +02:00

..

protocols

refactor(host/W6.2): extract the input-injection backends into the pf-inject crate

2026-07-17 11:52:02 +02:00

src

fix(host/windows): the pad service thread no longer waits on pnputil at its leisure

2026-07-30 23:35:32 +02:00

Cargo.toml

chore(unsafe): the workspace adopts the drivers' unsafe discipline

2026-07-28 21:31:41 +02:00