You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 59849f9
Browse filesBrowse the repository at this point in the historyBrowse files
fix(shared): probe PATH candidates when a directory listing fails
Only three failure reasons prove a PATH entry can never hold a command: NotFound (ENOENT), BadResource (ENOTDIR/EISDIR/ELOOP) and BadArgument. Everything else — EBUSY, EIO and EPERM, the last two arriving unclassified as Unknown — is transient or unproven, and treating it as an empty listing ruled out every candidate without the stat fallback and cached that false negative for the full 30s window, so an installed command could briefly appear missing. Unproven failures now list as null, which makes the caller probe candidates directly the way it did before this cache existed.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
0 commit comments