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

[Bug] Model Management shows providers but no models (empty model list) in Copilot Eclipse

Cerrado
#486 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

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
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
java
Área
ai, desktop-dev

Línea de trabajo

The payload names no source file, so start by reproducing: open the GitHub Copilot Model Management view in Eclipse and confirm providers appear with no models beneath them. The logs show AutoModelService fetching a model, so compare what the language server returns with what the view renders to find where the list is dropped. Done means models appear under each provider and the empty state is shown clearly when none are available.

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

Descripción

bug

copilot web wrote that for me:
Environment

Eclipse: 2026-09 (4.41.0), buildId=4.41.0.20260903-0719
OS: Linux x86_64 / GTK
Java: 25.0.4.1 (Eclipse Adoptium)
GitHub Copilot plugin version: GitHub Copilot 0.21.0.202608060743
Previously tested nightly: 0.21.0.202610121610_nightly
Workspace: /home/chris/Dokumente/eclipse24cpp

Summary The GitHub Copilot Eclipse plugin starts successfully, signs in, and chat requests work, but the Model Management UI shows providers without any model entries beneath them. The user can chat, but cannot select a model (e.g. Claude) from the model picker.

Steps to reproduce

Install GitHub Copilot plugin in Eclipse.
Sign in to GitHub Copilot.
Open Window → Show View → Other… → GitHub Copilot → Model Management.
Expand one or more providers (Anthropic / OpenAI / Microsoft / Fireworks / etc.).
Observe that only provider names are visible; no model names are listed underneath.

Expected behavior

Model names should appear underneath each provider and be selectable by the user.
The selected model should be available for chat/completion requests.
If a provider is unsupported or a model is unavailable, the UI should show that state clearly rather than rendering an empty list.

Actual behavior

Providers are shown, but no models are shown under them.
Chat still works, and the language server successfully resolves sessions and fetches an auto model. However the model management UI is empty.

Relevant log excerpts

Auth/session: !ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:50:39.303 !MESSAGE [LS:GitHub Copilot Language Server][Info] [AuthManager] resolvePersistedSession: no active session editorId=eclipse pickerEnabled=false optedOut=true autoAdoptAttempted=false

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:50:39.307 !MESSAGE [LS:GitHub Copilot Language Server][Info] [AuthManager] resolveSession: persisted store returned no session

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:51:05.907 !MESSAGE [LS:GitHub Copilot Language Server][Info] [AuthManager] signInEditor: persisted editorId=eclipse tokenId=1 rewrite=true

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:51:05.917 !MESSAGE [LS:GitHub Copilot Language Server][Info] [AuthManager] resolveSession: resolved from transient session

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:51:06.929 !MESSAGE [LS:GitHub Copilot Language Server][Info] [AutoModelService] Auto model cache cleared due to token update

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:57:20.905 !MESSAGE [LS:GitHub Copilot Language Server][Info] [AuthManager] resolveSession: persisted store resolved a session

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:57:26.870 !MESSAGE [LS:GitHub Copilot Language Server][Info] [AutoModelService] Auto model cache cleared due to token update

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:57:26.871 !MESSAGE [LS:GitHub Copilot Language Server][Info] [CopilotMCP] MCP state changed from false to true

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:57:26.903 !MESSAGE [LS:GitHub Copilot Language Server][Info] [AuthManager] resolveSession: persisted store resolved a session

Successful language server startup: !ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:57:20.642 !MESSAGE [LS:GitHub Copilot Language Server][Info] [lsp] GitHub Copilot Language Server 1.527.0 initialized

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:57:24.573 !MESSAGE [LS:GitHub Copilot Language Server][Info] [GithubAvailableEmbeddingTypes] Got embeddings. Primary: metis-1024-I16-Binary. Deprecated:

Auto model fetch works: !ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:57:26.871 !MESSAGE [LS:GitHub Copilot Language Server][Info] [AutoModelService] Auto model cache cleared due to token update

!ENTRY org.eclipse.lsp4e 1 0 2026-10-14 11:57:26.911 !MESSAGE [LS:GitHub Copilot Language Server][Info] [BackgroundAgent] GitHub identity changed, clearing cached sessions { hadPrevious: false, hasCurrent: true, cachedSessionCount: 0, remoteDelegateCount: 0 }

(In another run, the server logs included “AutoModelService] Fetched auto model for active in 126ms: gpt-5-mini” and successful chat/completion requests returning HTTP 200.)

Additional notes

We tried both nightly and stable plugin builds; the issue remained.
Secure Storage was unlocked; auth persisted after sign-in.
Chat/completion requests are successful, so backend auth and connectivity are functioning.
This appears to be a UI/model-list rendering issue rather than an auth or billing issue.

I’d appreciate any guidance or a fix. If possible, please provide a patch or a workaround for the Model Management view. Also, it would be useful if the UI could show model availability or a clear error when the model list is empty instead of silently showing only providers.

One more thing:

The issue is not a free-plan restriction. The language server is authenticated and fetches an auto model successfully.
This appears to be inside the Copilot Eclipse client (UI) and/or the mapping between model metadata returned by the server and the view that renders it.

Thank you.

Lenguaje dominante
Java
Estrellas
128
Forks
66
Merge medio
1 d 16 h
PR fusionados (30 d)
11

Preparar el entorno

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/copilot-for-eclipse

Todos los issues de microsoft/copilot-for-eclipse

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.