plugin_hash_failed
Diagnostic `nanook::plugin::hash_failed`
Summary
failed to hash plugin `{0}`: {1}
Help
verify the file is readable by the running uid
Details
When this fires
Policy::admit tried to sha256 the cdylib bytes during the discovery walk and the read failed. The file showed up in read_dir but sha256_hex couldn't open or stream it. This bubbles up at load time as hash_failed rather than at discovery, so nanook plugins ls keeps listing the entry with Admission::Unhashable while the load attempt is the thing that errors.
What to check
The running uid needs read on the cdylib. A racing rebuild can also delete the file between discovery and load. For flaky storage (NFS, dead mounts) check dmesg.