redhat-developer / redhat-developer/vscode-xml
Problem with activation on WSL
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 328
- Forks
- 101
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 7
Description
Type: Bug
The extension simply does not activate on WSL, in the "Running extensions" section it hangs forever with the status "Activating..."
Extension version: 0.26.2024031808
VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2
System Info
| Item | Value |
|---|---|
| CPUs | 12th Gen Intel(R) Core(TM) i7-12700H (20 x 2688) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.71GB (13.22GB free) |
| Process Argv | |
| Screen Reader | yes |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | WSL: Ubuntu |
| OS | Linux x64 5.15.146.1-microsoft-standard-WSL2 |
| CPUs | 12th Gen Intel(R) Core(TM) i7-12700H (20 x 2687) |
| Memory (System) | 15.48GB (10.44GB free) |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | WSL: Ubuntu |
| OS | Linux x64 5.15.146.1-microsoft-standard-WSL2 |
| CPUs | 12th Gen Intel(R) Core(TM) i7-12700H (20 x 2687) |
| Memory (System) | 15.48GB (10.44GB free) |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | WSL: Ubuntu |
| OS | Linux x64 5.15.146.1-microsoft-standard-WSL2 |
| CPUs | 12th Gen Intel(R) Core(TM) i7-12700H (20 x 2687) |
| Memory (System) | 15.48GB (10.44GB free) |
| 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
Reproduce the extension's indefinite “Activating...” state in VS Code 1.87.2 while connected to WSL: Ubuntu, using the reported extension and remote OS versions. Start by inspecting the extension activation path and available activation logs; done means the extension activates normally in WSL and no longer remains stuck in the Running extensions view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100