fix(terminal): stop proot "can't sanitize binding" fd warnings

[RohitKushvaha01]

proot canonicalizes every -b host path with realpath(3). The /proc/self/fd/N magic links only resolve when the descriptor points to a real file, so piped stdio (what Acode's ProcessBuilder uses) made realpath(3) fail and proot drop the binding with can't sanitize binding "/proc/self/fd/N".

The [ -e ] guard passed those links because stat(2) follows the magic link to the underlying pipe/socket inode, so it never filtered them out. Replace it with a can_bind helper that resolves the link target the way realpath(3) does, and narrow the LSP-side proot-warning filters to only this benign message so real proot warnings are no longer swallowed.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; the follow-up descriptor probing change preserves the process identity and descriptors that proot receives.

Summary

• Adds a shell helper that admits only descriptor links resolving to existing absolute paths.
• Uses the sourcing shell’s PID so descriptor inspection is unaffected by readlink’s child-process redirection.
• Restricts both LSP warning filters to the known benign /proc/self/fd binding warning.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Inspect shell descriptor via /proc/SELF_PID/fd/N] --> B{Descriptor target}
  B -->|Existing absolute path| C[Add proot binding]
  B -->|Pipe, socket, anonymous inode, or missing path| D[Skip binding]
  C --> E[Exec proot with inherited PID and descriptors]
  D --> E
  E --> F[LSP receives process output]
  F --> G{Known fd-binding warning?}
  G -->|Yes| H[Suppress benign warning]
  G -->|No| I[Surface output normally]

Loading

_{Reviews (2) · Last reviewed commit: "fix(terminal): probe /proc/self/fd via s..."}

[RohitKushvaha01]

@greptile