Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Failed to fetch models from Microsoft Foundry catalog Error: read ECONNRESET

Abierto
#867 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
azure, vscode
Área
devtools

Línea de trabajo

The stack trace points into the bundled extension's dist/extension.js (listModels and fetchCatalogModels), and the failing call is a POST to https://api.catalog.azureml.ms/asset-gallery/v1.0/models. Search the repository for asset-gallery or api.catalog to find the code that builds this request, then try to reproduce the ECONNRESET outside VS Code. Done means the failure is either fixed or traced to a specific request, with the cause written up on the issue.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

needs attention

I link my VSCode Azure extension to my Azure subscription. Then open Foundry project in Foundry Toolkit extension. It loads all project resources. I haven't models yet. Go under my resources group -> Models. No models loaded (OK). The terminal show:

  • 2026-10-15 17:18:19.672 [info] Loading View: modelsOverview

I have three tabs: Foundry, Others, Catalog. Now I push in Catalog. At this point, some models are loaded but not hosted by Foundry. In terminal see this error:

2026-10-15 17:19:33.594 [error] Failed to fetch models from Microsoft Foundry catalog Error: read ECONNRESET
at jn.from (c:\Users\userTest.vscode\extensions\ms-windows-ai-studio.windows-ai-studio-1.6.16-win32-x64\dist\extension.js:5886:1548)
at A. (c:\Users\userTest.vscode\extensions\ms-windows-ai-studio.windows-ai-studio-1.6.16-win32-x64\dist\extension.js:5887:20963)
at A.emit (node:events:514:28)
at a. (c:\Users\userTest.vscode\extensions\ms-windows-ai-studio.windows-ai-studio-1.6.16-win32-x64\dist\extension.js:1996:14022)
at ClientRequest.emit (node:events:526:24)
at emitErrorEvent (node:_http_client:114:11)
at TLSSocket.socketErrorListener (node:_http_client:766:5)
at TLSSocket.emit (node:events:526:24)
at emitErrorNT (node:internal/streams/destroy:170:8)
at emitErrorCloseNT (node:internal/streams/destroy:129:3)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
at gu.request (c:\Users\userTest.vscode\extensions\ms-windows-ai-studio.windows-ai-studio-1.6.16-win32-x64\dist\extension.js:5889:2369)
at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
at async a.listModels (c:\Users\userTest.vscode\extensions\ms-windows-ai-studio.windows-ai-studio-1.6.16-win32-x64\dist\extension.js:4916:26592)
at async C.fetchCatalogModels (c:\Users\userTest.vscode\extensions\ms-windows-ai-studio.windows-ai-studio-1.6.16-win32-x64\dist\extension.js:4941:13758)
at async C.listModels (c:\Users\userTest.vscode\extensions\ms-windows-ai-studio.windows-ai-studio-1.6.16-win32-x64\dist\extension.js:4941:11587)
at async C.listModels (c:\Users\userTest.vscode\extensions\ms-windows-ai-studio.windows-ai-studio-1.6.16-win32-x64\dist\extension.js:4942:25937)
at async c:\Users\userTest.vscode\extensions\ms-windows-ai-studio.windows-ai-studio-1.6.16-win32-x64\dist\extension.js:3452:25736

I analyze the error and seems it's trying to access this url like POST:

I don't know if something left or fails, but I can't use models from VSCode extension. From Foundry portal it works fine.
Thanks

Lenguaje dominante
JavaScript
Estrellas
2.1k
Forks
262
Merge medio
1 d 4 h
PR fusionados (30 d)
28

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/foundry-dev-tools

Todos los issues de microsoft/foundry-dev-tools

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.