Vs automation issue
Maintainers usually reply within 1 day
@JerryYangKai is already working on this.
Since Sep 28, 2026.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript, vscode
- Domain
- devtools
Research direction
Start with the ai-mlstudio.openInVSCodeAzure command and the extension.js entries in the call stack, then try to reproduce the JSON parsing failure using the reported VS Code and extension versions. Trace the input associated with the reported position and verify that the command completes without the SyntaxError.
Written by the indexing model from the issue text.
Description
Does this occur consistently?
Repro steps:
Action: ai-mlstudio.openInVSCodeAzure
Error type: SyntaxError
Error Message: Unexpected non-whitespace character after JSON at position 1205 (line 2 column 1)
Version: 1.6.14
OS: linux
OS Arch: x64
OS Release: 6.1.146.1-microsoft-standard
Product: Visual Studio Code
Product Version: 1.139.1
Language: pl
UTC time: Sun, 27 Sep 2026 10:01:57 GMT
Call Stack
v.beforeRun extension.js:2390:2469
v.process extension.js:2390:2265
s.open extension.js:2390:12507
extension.js:2160:25836extension.js:2160:25836
extension.js:2158:22927extension.js:2158:22927
async o extension.js:1908:19248
extension.js:1910:17503extension.js:1910:17503
async bf._executeContributedCommand extensionHostProcess.js:164:48874
- 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
-
needs attention
Difficulty 4/5 3-5 days Newbie friendliness 22/100
microsoft/foundry-dev-tools#864 · 3 comments ·
Maintainers usually reply within 1 day
-
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
All issues in microsoft/foundry-dev-tools
Similar issues
-
Four problem loader browser tests fail on WindowsPossibly taken @Patriciaath999 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
juice-shop/juice-shop#3686 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ScottKirvan/GOMAC#56 ·
-
area:install bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
yetone/magpie#2406 · 1 comment ·
Maintainers usually reply within 1 day