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

YAPAY

Closed
#860 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

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
tooling

Research direction

Start by tracing the ai-mlstudio.openInVSCodeAzure command to the beforeRun call shown in the stack trace, then inspect how it parses JSON. The report gives no reproduction steps or expected result, so first reproduce the error and identify the malformed input. Done means the command handles the reported JSON parsing case correctly and a regression check covers it.

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 833 (line 1 column 834)

Version: 1.6.15
OS: linux
OS Arch: x64
OS Release: 6.1.158.2-microsoft-standard
Product: Visual Studio Code
Product Version: 1.141.0
Language: tr
UTC time: Mon, 12 Oct 2026 16:21:05 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 Rf._executeContributedCommand extensionHostProcess.js:165:49173
Dominant language
JavaScript
Stars
2.1k
Forks
260
Avg merge
1d 50m
Merged PRs (30d)
32

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.