Gradle: Synchronize Gradle projects with workspace failed due to an error connecting to the Gradle build.
@CsCherrYY is already working on this.
Since Apr 7, 2022.
Assessment
This issue has not been assessed yet.
Description
Caused by: org.gradle.internal.service.ServiceCreationException: Could not initialize native services.
at org.gradle.internal.nativeintegration.services.NativeServices.initialize(NativeServices.java:159)
at org.gradle.internal.nativeintegration.services.NativeServices.initializeOnClient(NativeServices.java:135)
at org.gradle.tooling.internal.provider.DefaultConnection.initializeServices(DefaultConnection.java:115)
at org.gradle.tooling.internal.provider.DefaultConnection.configure(DefaultConnection.java:101)
at org.gradle.tooling.internal.consumer.connection.AbstractPost12ConsumerConnection.configure(AbstractPost12ConsumerConnection.java:37)
at org.gradle.tooling.internal.consumer.loader.DefaultToolingImplementationLoader.createConnection(DefaultToolingImplementationLoader.java:106)
at org.gradle.tooling.internal.consumer.loader.DefaultToolingImplementationLoader.create(DefaultToolingImplementationLoader.java:86)
at org.gradle.tooling.internal.consumer.loader.CachingToolingImplementationLoader.create(CachingToolingImplementationLoader.java:45)
at org.gradle.tooling.internal.consumer.loader.SynchronizedToolingImplementationLoader.create(SynchronizedToolingImplementationLoader.java:44)
at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.onStartAction(LazyConsumerActionExecutor.java:160)
at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:142)
at org.gradle.tooling.internal.consumer.connection.CancellableConsumerActionExecutor.run(CancellableConsumerActionExecutor.java:45)
- Dominant language
- TypeScript
- Stars
- 352
- Forks
- 166
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 32
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.
More from microsoft/vscode-java-pack
-
Memory Leak in Linux Openai-triaged bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/vscode-java-pack#1543 · 8 comments · 4 reactions ·
-
ai-triaged bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/vscode-java-pack#1443 · 1 comment · 2 reactions ·
-
ai-triaged bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoft/vscode-java-pack#1425 · 1 comment ·
-
ai-triaged enhancement feature-request
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/vscode-java-pack#1423 · 2 comments · 1 reaction ·
-
ai-triaged area/jdtls bug needs-investigation
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/vscode-java-pack#1420 · 1 comment ·
All issues in microsoft/vscode-java-pack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·