microsoft / microsoft/vscode-java-dependency
Extension activates wrongly on running user tasks
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 199
- Forks
- 105
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 27
Description
Type: Bug
I have a user task configured in vscode to run upon a certain shortcut (launching some external editor on the currently open folder).
A few vscode versions ago, this user task was sometimes not activating anymore. However when waiting a long time I noticed that the user task would work but always super slowly and a notification in vscode saying that it activates the java extension (though my projects have nothing to do with java and the user task neither, it just launches an external editor on the current workspace folder).
The vscode extension bisect command revealed the java extension as being the culprit.
(maybe related to https://github.com/microsoft/vscode/issues/175833)
Extension version: 0.21.2
VS Code version: Code 1.77.0 (7f329fe6c66b0f86ae1574c2911b681ad5a45d63, 2023-03-29T09:57:11.797Z)
OS version: Darwin x64 22.3.0
Modes:
Sandboxed: No
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled metal: disabled_off multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off |
| Load (avg) | 5, 4, 3 |
| Memory (System) | 32.00GB (0.86GB free) |
| Process Argv | --crash-reporter-id 83993668-ab1b-4a86-9124-7b327487db9f |
| Screen Reader | no |
| VM | 0% |
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 delay with the reported VS Code user task and use the VS Code extension bisect result to confirm the Java extension is involved. Check the extension activation behavior against the related VS Code issue; done means unrelated user tasks no longer activate or wait for the Java extension.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100