microsoft / microsoft/vscode-languageserver-node
Language Client to should log `stderr` on launch failures
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 404
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 14
Description
There was a issue with one of the libraries we use for Jedi language server. The error object that we got from client.start() did not have the right info the diagnose the problem. The problem was reported to stderr, and that was captures it would have been easier to diagnose.
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 the Language Client client.start() launch-failure path and inspect how the error object is assembled. Reproduce a launch failure involving the Jedi language server, then verify that captured stderr is included in the diagnostic information available to the caller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100