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

y

Open
#863 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
18/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
azure, javascript, vscode
Domain
cloud, tooling

Research direction

The failing action is pickAgentAndCreateFoundryEvalWithCopilot, and the stack trace goes through a getPage pagination call that returns a 400 with SubscriptionNotRegistered. Start by finding where that action calls the Foundry API and how paginated requests handle errors. The issue lacks repro steps, so first confirm the failure with a subscription that has the required resource provider registered. Done means the error is either handled with a clear message or the request no longer fails for a registered subscription.

Written by the indexing model from the issue text.

Description

needs attention

Does this occur consistently?
Repro steps:

Action: pickAgentAndCreateFoundryEvalWithCopilot
Error type: SubscriptionNotRegistered
Error Message: Pagination failed with unexpected statusCode 400

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: de
UTC time: Tue, 13 Oct 2026 07:16:43 GMT

Call Stack
v extension.js:5877:39507
b extension.js:5691:12873
h extension.js:5693:139
Object.getPage extension.js:5692:291256
async p extension.js:5692:291802
async o extension.js:5692:291736
async h.pickAgentAndCreateFoundryEvalWithCopilot extension.js:2510:218
extension.js:2423:55513extension.js:2423:55513
async o extension.js:1908:19248
extension.js:2423:55408extension.js:2423:55408
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

  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.