redhat-developer / redhat-developer/lsp4ij
Capture LSP traces per language server and write them to a log file
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 344
- Forks
- 113
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 15
Description
Required a mechanism to capture LSP traces for each individual language server and persist them into log files.
Currently, trace output is only visible in the Language Server Console, which makes debugging intermittent failures difficult - especially in CI environments. Capturing and exporting the traces would help with root-cause analysis and reproducibility of issues.
Contributor guide
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 by tracing how LSP trace output currently reaches the Language Server Console and identify the boundary for each individual language server. Done means traces are persisted to log files per language server and can support debugging intermittent failures in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100