Unable to use Foundry Toolkit when VS Code started from WSL
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 22/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- ubuntu, vscode
- Domain
- devtools
Research direction
The failure is the "My Resources" view reporting "There is no data provider registered" when VS Code runs in a WSL remote session, while the same extension works on Windows. Start by reproducing it with VS Code connected to WSL Ubuntu and checking whether the extension activates and registers that view's data provider, using the trace logs the reporter mentions. Done means the view loads its data inside WSL, or the cause is pinned down and documented.
Written by the indexing model from the issue text.
Description
Foundry Toolkit 1.6.15, VS Code 1.141.1, WSL Ubuntu-24.04
“My Resources” shows "There is no data provider registered that can provide view data"
The same installation works in Windows.
I have tried reloading the window, reinstalling, rebooting, setting log level for the extension to trace, and using Github Copilot to diagnose, but unable to resolve problem.
Fresh install of WSL, Ubuntu, VS Code and Foundry Toolkit
- Dominant language
- JavaScript
- Stars
- 2.1k
- Forks
- 260
- Avg merge
- 1d 6m
- Merged PRs (30d)
- 33
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/foundry-dev-tools
-
yOpenneeds attention
Difficulty 4/5 1-2 days Newbie friendliness 18/100
microsoft/foundry-dev-tools#863 · 1 comment ·
Maintainers usually reply within 1 day
-
Support Foundry Canvas in VS CodePossibly taken @qinezh claimed this 2 days ago. Opencanvas
microsoft/foundry-dev-tools#861 · 4 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Foundry Toolkit and Foundry Local Model issuePossibly taken @a1exwang claimed this 2 days ago. Openneeds attention
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/foundry-dev-tools#854 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Unable to open Foundary Project In VS CodePossibly taken @JerryYangKai claimed this 1 day ago. Openinvestigating
Difficulty 3/5 1-2 days Newbie friendliness 42/100
microsoft/foundry-dev-tools#848 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
azure ai vscode connection issuePossibly taken @JerryYangKai claimed this 13 days ago. Openinvestigating
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/foundry-dev-tools#844 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
All issues in microsoft/foundry-dev-tools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 8 days
-
docs(stream-protocol): document messageMetatadata on start/finish and the message-metadata chunkOpenfactory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
feature request
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
docs hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
pacocartones/free-llm-api-hub#347 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
wpilibsuite/wpilib-docs#3378 ·
Maintainers usually reply within 1 day