redhat-developer / redhat-developer/vscode-java
The project DataflowTemplates can't be parsed when opened by VSCode from WSL
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
The project https://github.com/GoogleCloudPlatform/DataflowTemplates can't be parsed when opened by VSCode from WSL
Environment
- Operating System: Windows 11 / WSL Ubuntu 22
- JDK version: 17.0.8.1
- Visual Studio Code version: 1.83.1
- Java extension version: 1.24.0
Steps To Reproduce
- clone https://github.com/GoogleCloudPlatform/DataflowTemplates to a WSL directory
- open in VSCode via "code ."
Current Result
All the Java subprojects in the "v2" subfolder are red.
The "Language Support for Java" log contains multiple errors like
[Error - 7:19:34 PM] Oct 27, 2023, 7:19:34 PM Problems occurred when invoking code from plug-in: "org.eclipse.jdt.ls.core".
structured-logging does not exist
Java Model Exception: Error in Java Model (code 969): structured-logging does not exist
at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:550)
at org.eclipse.jdt.internal.core.JavaModelManager.getPerProjectInfoCheckExistence(JavaModelManager.java:2567)
...
Jumps to type definitions don't work.
language-server-log.txt
Expected
devtools-console-log.txt
Result
The project is parsed correctly, no errors detected, all the jumps to type definitions work.
Additional Informations
cat /proc/sys/fs/inotify/max_user_watches
524288
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 reproducing the report with the DataflowTemplates repository in a WSL Ubuntu directory, opening its v2 subprojects through VSCode with "code .". Read the attached language-server-log.txt and devtools-console-log.txt, then compare the result with the expected behavior: no parsing errors and working jumps to type definitions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100