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

HATA

Open
  • Is something wrong?
#833 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@JerryYangKai is already working on this.

Since Oct 2, 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 call-stack locations around v.beforeRun, v.process, and s.open. Reproduce the command on the reported Linux and VS Code versions, then trace the JSON input that produces the SyntaxError. Done means the command no longer fails with this parsing error and the regression is covered by an appropriate test.

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 815 (line 2 column 1)

Version: 1.6.14
OS: linux
OS Arch: x64
OS Release: 6.1.158.2-microsoft-standard
Product: Visual Studio Code
Product Version: 1.139.1
Language: tr
UTC time: Mon, 28 Sep 2026 05:00:23 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
9h 41m
Merged PRs (30d)
38

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

  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.