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

GitLab errors hide glab's stderr behind a generic "GitLab CLI command failed"

Abierto Apto para principiantes
  • ¿Algo no está bien?
#22,342 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Sinan53x ya está trabajando en esto.

Desde el 20/10/2026.

  • #22509 de @Sinan53x — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
73/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
gitlab, typescript
Área
backend, developer-experience

Línea de trabajo

Lee packages/source-control-gitlab/src/server/GitLabCli.ts y compara su gestión de errores con el cambio de git stderr en #5620. Sigue cómo VcsProcessExitError llega a GitLabCliCommandError.detail, incluida la asignación not-found en fromVcsError. El objetivo es que el stderr útil de glab aparezca en el error mostrado y que se mantenga la gestión de los errores de autenticación, límite de solicitudes y spawn.

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

Descripción

What happened

In the desktop app, a self-hosted GitLab repo keeps showing Source control provider gitlab failed in listChangeRequests: GitLab CLI command failed. The app also can't create merge requests. Nothing in the UI says what glab actually returned, so the user can't tell whether this is a T3 Code problem, a glab problem or a GitLab server problem.

Diagnosis

The real cause was outside T3 Code. The company nginx reverse proxy in front of GitLab decodes %2F in API paths. So GET /api/v4/projects/<group>%2F<project> returns 404 for every project, while GET /api/v4/projects/<id> works. glab mr list in the repo fails with 404 Not Found.

T3 Code shows none of that. In packages/source-control-gitlab/src/server/GitLabCli.ts, GitLabCliCommandError.detail is a fixed string ("GitLab CLI command failed."). The VcsProcessExitError cause, which holds glab's stderr, only appears in the server trace. fromVcsError also maps failureKind: "not-found" to the same generic error. The ThreadSettlementServiceV2.sweep / ThreadPullRequestServiceV2.synchronize branch-MR lookup calls this again and again (about 4,100 failures in roughly 1.5 h in the trace), and every failure looks the same.

Suggestion: put a trimmed first line of glab's stderr into GitLabCliCommandError.detail/message, as #5620 did for git (fix(vcs): surface git's stderr on GitCommandError). For example: GitLab CLI command failed: 404 Not Found.

Steps to reproduce
  1. Use a self-hosted GitLab behind a reverse proxy that decodes %2F (e.g. nginx proxy_pass http://backend/;). Any glab failure that isn't auth, rate limit or spawn works too.
  2. glab auth login to that host (glab auth status shows the host as logged in).
  3. Open a repo with an https://<host>/<group>/<project>.git remote in the T3 Code desktop app.
  4. Watch the source control / MR area: GitLab CLI command failed. with no detail. Run glab mr list in the repo: 404 Not Found.
Version

0.1.0 (desktop app; local server reports serverVersion 0.1.0). Also checked against main at 23b550dd: same code.

Environment

Windows 11 Pro 10.0.26200 x64, Node v26.8.2, glab 1.123.0, self-hosted GitLab behind nginx

Evidence
SourceControlProviderError: Source control provider gitlab failed in listChangeRequests: GitLab CLI command failed.
  at findLatestPrForHeadContext ... lookupBranchPullRequest ... branchPullRequest
  at ThreadSettlementServiceV2.pullRequestFor ... ThreadSettlementServiceV2.sweep
  [cause]: GitLabCliCommandError: GitLab CLI failed in execute: GitLab CLI command failed.
    [cause]: VcsProcessExitError: VCS process failed in GitLabCli.execute: glab (<repo>) exited with 1 - Merge request not found.

$ glab mr list --source-branch main
ERROR  404 Not Found.

$ glab api "projects/<group>%2F<project>"   -> HTTP 404
$ glab api "projects/<id>"                  -> 200 OK
Related issues

#15660 (closed; generic "GitLab CLI command failed" on old GitLab, where the cause was also hidden). #5620 (same fix for git). #20226 and #7849 are about building GitLab project paths. None of them asks to show glab's stderr.

Fix applied or workaround

None in T3 Code. The GitLab admin was asked to fix the nginx proxy_pass so %2F isn't decoded.

Filed by

Claude Code (claude-opus-5-5) via t3 triage

Lenguaje dominante
TypeScript
Estrellas
24.8k
Forks
6.4k
Merge medio
3 h 39 min
PR fusionados (30 d)
301

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 pingdotgg/t3code

Todos los issues de pingdotgg/t3code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.