crytic / crytic/contract-explorer

Error: spawn slither-lsp ENOENT (PATH issue)

Open
#52 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
36
Forks
8
PR merge metrics
No merged PRs in 30d

Description

Hey, just bringing it up to your attention.

[This PR is still relevant](https://github.com/crytic/contract-explorer/pull/45). Extension has problem finding [slither-lsp](https://github.com/crytic/contract-explorer/blob/789dc17aedab7268e2719b048fa751c0fed509d1/src/slitherLanguageClient.ts#L18), even if `echo $PATH` lists appropriate directories (and, `slither-lsp` is installed). This happens for both global and venv active python interpreter.

The only way to run extension, for me, was to do the [dev-installation](https://github.com/crytic/contract-explorer/blob/master/DEV.md) and point to the specific slither-lsp server running. However, even with that, the currently released version seems to be missing some functionality. Below is the only visible display. Plugin doesn't seem to do anything else than just allowing to toggle options for detection filters.

![contract-explorer](https://github.com/crytic/contract-explorer/assets/56428630/f35daf87-c038-44ab-a0c7-790738e3de2f)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with src/slitherLanguageClient.ts at the referenced line and compare the behavior with PR 45. Review DEV.md and test how the released extension locates slither-lsp under global and virtual-environment Python setups; done means the extension starts with an installed server and exposes the expected functionality.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, typescript, vscode
Domain
devtools, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.