Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta Adatta ai principianti
  • Qualcosa non va?
#22,342 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Sinan53x ci sta già lavorando.

Dal 20/10/2026.

  • #22509 di @Sinan53x — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
73/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
gitlab, typescript
Ambito
backend, developer-experience

Direzione di ricerca

Leggi packages/source-control-gitlab/src/server/GitLabCli.ts e confronta la gestione degli errori con la modifica di git stderr in #5620. Segui come VcsProcessExitError raggiunge GitLabCliCommandError.detail, compresa la mappatura not-found in fromVcsError. L’obiettivo è che lo stderr utile di glab compaia nell’errore mostrato, mantenendo la gestione degli errori di autenticazione, limite di richieste e spawn.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
TypeScript
Stelle
24.8k
Fork
6.4k
Merge medio
10h 8m
PR unite (30g)
323

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pingdotgg/t3code

Tutte le issue di pingdotgg/t3code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.