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

test

Open
  • Is something wrong?
#846 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
azure, javascript
Domain
cloud, devtools

Research direction

Start with G.createCognitiveServiceAccount at extension.js:2148 and the newProjectWithAccount call at extension.js:2390; the reported action is ai-mlstudio.viewContext.switchDefaultProject. The error says the subscription is not registered for Microsoft.CognitiveServices, but the issue gives no reproduction steps or expected behavior. First establish a reliable reproduction and clarify what behavior is expected before defining done.

Written by the indexing model from the issue text.

Description

needs attention

Does this occur consistently?
Repro steps:

Action: ai-mlstudio.viewContext.switchDefaultProject
Error type: Error
Error Message: Failed to create cognitive services account, HTTP Code 409, Error {"error":{"code":"MissingSubscriptionRegistration","message":"The subscription is not registered to use namespace 'Microsoft.CognitiveServices'. See https://aka.ms/rps-not-found for how to register subscriptions.","details":[{"code":"MissingSubscriptionRegistration","target":"Microsoft.CognitiveServices","message":"The subscription is not registered to use namespace 'Microsoft.CognitiveServices'. See https://aka.ms/rps-not-found for how to register subscriptions."}]}}

Version: 1.6.15
OS: win32
OS Arch: x64
OS Release: 10.0.22631
Product: Visual Studio Code
Product Version: 1.133.0
Language: en
UTC time: Tue, 06 Oct 2026 08:48:30 GMT

Call Stack 
G.createCognitiveServiceAccount extension.js:2148:26162
async a.newProjectWithAccount extension.js:2390:19325
extension.js:2390:18995extension.js:2390:18995
Dominant language
JavaScript
Stars
2.1k
Forks
260
Avg merge
10h 48m
Merged PRs (30d)
34

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.