OmniSharp / OmniSharp/csharp-language-server-protocol
Unable to start language server (?)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 638
- Forks
- 109
- Avg merge
- 1m
- Merged PRs (30d)
- 2
Description
I'm considering using the OmniSharp LanguageServer for one of my projects, but was unable to get the server to start. I read all of the documentation I could find and followed the implementation of the sample server, but still could not figure out what was wrong. I even tried running the sample server as-is, but could not get that to work.
The application gets as far as line 246 in LanguageServer.cs, where it will await _initializingTask.ConfigureAwait(false);, which never runs to completion.
At this point, the server does not respond to any messages passed on the input stream. Connecting with a client (lsp4intellij) fails, and sending an initialisation message manually by pasting it into stdin yields no response. It does not even give you any errors if you send a malformed message or just plain gibberish.
I'm running this on MacOS 13.0, and tried both .NET 6.0 and 7.0.
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 at line 246 of LanguageServer.cs, where the server awaits _initializingTask, and reproduce the sample server failure using the stdin input path described in the issue. Compare the sample server's initialization flow with the behavior on macOS under .NET 6 or 7. Done means the server completes initialization and responds to a valid initialization message, with malformed input producing observable handling rather than silence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100