jaredly / jaredly/reason-language-server
Reason Language Server crashed won't be restarted on Windows Vscode
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 649
- Forks
- 85
- PR merge metrics
- No merged PRs in 30d
Description
I have installed the reason-vscode extension and reinstalled plus enabled&disabled. I am getting always following an error, when I enable the extension and reload the workspace.
```
[Info - 1:52:50 AM] Connection to server got closed. Server will restart.
[Info - 1:52:51 AM] Connection to server got closed. Server will restart.
[Info - 1:52:51 AM] Connection to server got closed. Server will restart.
[Info - 1:52:51 AM] Connection to server got closed. Server will restart.
[Error - 1:52:51 AM] Connection to server got closed. Server will not be restarted.
The Reason Language Server server crashed 5 times in the last 3 minutes. The server will not be restarted.
Source: reason-vscode (Extension)
```
I can not find the file `reason-language-server.exe` is it called `bin.exe` now? However there is this file bin.exe in the the vscode extension directory of this extension. Why it named like `bin.exe`? If I would lookup what processes are running, then a process called bin.exe would not associate it with this extension and might think of malware.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reason-vscode extension behavior on Windows and the reported reason-language-server.exe versus bin.exe naming. Reproduce the repeated crash and restart limit from the issue, then determine whether the executable naming or the server crash is responsible. Done means the language server starts reliably and the executable is clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml, vscode
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100