Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

fix

Closed
  • Is something wrong?
#795 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@JerryYangKai is already working on this.

Since Sep 22, 2026.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
javascript, vscode
Domain
devtools

Research direction

Start by reproducing the ai-mlstudio.openInVSCodeAzure action in Visual Studio Code 1.138.0 on Linux, using the reported extension.js stack locations as the initial trace. Inspect the JSON consumed around extension.js:2390 and identify the input that produces the SyntaxError; done means the action completes without this parse error.

Written by the indexing model from the issue text.

Description

needs attention

Does this occur consistently?
Repro steps:

Action: ai-mlstudio.openInVSCodeAzure
Error type: SyntaxError
Error Message: Unexpected non-whitespace character after JSON at position 1271 (line 2 column 1)

Version: 1.6.13
OS: linux
OS Arch: x64
OS Release: 6.1.158.2-microsoft-standard
Product: Visual Studio Code
Product Version: 1.138.0
Language: en
UTC time: Fri, 18 Sep 2026 09:06:09 GMT

Call Stack 
y.beforeRun extension.js:2390:2469
y.process extension.js:2390:2265
s.open extension.js:2390:12507
extension.js:2160:21739extension.js:2160:21739
async o extension.js:1908:19260
extension.js:1910:17503extension.js:1910:17503
async pf._executeContributedCommand extensionHostProcess.js:555:48874
Dominant language
JavaScript
Stars
2.1k
Forks
260
Avg merge
8h 58m
Merged PRs (30d)
41

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/foundry-dev-tools

All issues in microsoft/foundry-dev-tools

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.