Unable to Upload & Index the PDF
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
Research direction
Start by reproducing the upload and indexing flow in Visual Studio Code 1.138.0 on Windows, then inspect the foundry-api.listVectorStores call and its 403 response using the provided stack trace. The issue is ready when the cause of the pagination failure is identified and the PDF upload/index flow no longer fails, with a regression test or clear reproduction details added.
Written by the indexing model from the issue text.
Description
Does this occur consistently?
Repro steps:
Action: foundry-api.listVectorStores
Error type: UserError
Error Message: Pagination failed with unexpected statusCode 403
Version: 1.6.14
OS: win32
OS Arch: x64
OS Release: 10.0.19045
Product: Visual Studio Code
Product Version: 1.138.0
Language: en
UTC time: Tue, 29 Sep 2026 15:35:28 GMT
Call Stack
v extension.js:5877:39507
b extension.js:5691:12873
l extension.js:5692:139
Object.getPage extension.js:5691:100613
async f extension.js:5691:101062
async g extension.js:2148:179892
async C extension.js:2148:181436
async G.listPagedVectorStores extension.js:2148:43414
async r extension.js:2148:179713
async G.listVectorStores extension.js:2148:42945
async h.listVectorStores extension.js:2170:190
async u.listVectorStores extension.js:2387:18439
extension.js:2158:22927extension.js:2158:22927
extension.js:2148:189604extension.js:2148:189604
async o extension.js:1908:19248
async u extension.js:2148:189425
async r.fetch extension.js:4941:4161
async r._refresh extension.js:5569:16226
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/foundry-dev-tools
-
needs attention
Difficulty 4/5 3-5 days Newbie friendliness 12/100
microsoft/foundry-dev-tools#851 · 1 comment ·
Maintainers usually reply within 1 day
-
needs attention
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/foundry-dev-tools#850 · 1 comment ·
Maintainers usually reply within 1 day
-
needs attention
Difficulty 3/5 1-2 days Newbie friendliness 38/100
microsoft/foundry-dev-tools#849 · 1 comment ·
Maintainers usually reply within 1 day
-
needs attention
Difficulty 3/5 1-2 days Newbie friendliness 42/100
microsoft/foundry-dev-tools#848 · 1 comment ·
Maintainers usually reply within 1 day
-
errorOpenneeds attention
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/foundry-dev-tools#847 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoft/foundry-dev-tools
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
anoopcodehack/DevBoard#609 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
openai/codex-plugin-cc#813 ·
-
area: ops type: test
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
accensa/x402-facilitator-stellar#559 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bilawalsidhu/gods-eye-view#1060 ·
Maintainers usually reply within 1 day
-
Progress difficulty filter lists Hard before MediumPossibly taken @Pandamachi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sysprog21/codetrial#281 · 1 comment ·
Maintainers usually reply within 1 day