External tools are called without compatibility check
- Dominant language
- Go
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Before running `lsof` to find the list of open files, we should (at least):
- check that the command is present. If not, display information on how to install it (platform dependent)
- check if the version is compatible (output may change, maybe). We could use some fallbacks to collect as much information as possible, even though the version is not the one that we expect.
Contributor guide
No contributing guide indexed for this repository
Research direction
Locate the code that invokes `lsof`, then inspect how external command failures and output versions are currently handled. Define the supported version behavior and platform-specific installation guidance; done means missing or incompatible `lsof` is reported clearly and available fallbacks collect useful information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100