## Summary Since updating to VS Code 1.128.0, the extension can no longer authenticate against our self-managed GitLab instance. Both the OAuth flow and adding an account with a personal access token fail with: ``` FetchError: Invalid response body while trying to fetch https://gitlab.example.com/api/v4/user: Premature close ``` The OAuth flow itself completes in the browser; the failure happens afterwards when the extension fetches the current user. Authentication worked fine until now, and the GitLab instance itself is healthy (see verification below). This looks like the known Node 24.17.0 regression that breaks node-fetch v2 keep-alive/gzip responses: [nodejs/node#63989](https://github.com/nodejs/node/issues/63989) (see also [node-fetch#1767](https://github.com/node-fetch/node-fetch/issues/1767)). VS Code 1.128.0 ships Electron 42.5.0 with Node 24.17.0, which is exactly the affected version (24.16.0 is not affected). The error surfaces in the extension's bundled node-fetch `Gunzip` stream, matching that bug's signature. ## Steps to reproduce 1. VS Code 1.128.0 with GitLab Workflow 6.84.2, no existing account. 2. Run "GitLab: Authenticate" against a self-managed instance (OAuth). The browser flow succeeds. 3. Back in VS Code, an error notification appears: "Invalid response body while trying to fetch https://gitlab.example.com/api/v4/user: Premature close". 4. Alternatively, add the account with a PAT instead: same failure, this time on `/api/v4/personal_access_tokens/self`. ## Logs OAuth flow: ``` 2026-07-08T13:03:28:645 [error]: OAuth flow: Creating account from code failed: Invalid response body while trying to fetch https://gitlab.example.com/api/v4/user: Premature close FetchError: Invalid response body while trying to fetch https://gitlab.example.com/api/v4/user: Premature close at Gunzip.<anonymous> (~/.vscode/extensions/gitlab.gitlab-workflow-6.84.2/extension.js:177:332444) at Gunzip.emit (node:events:521:24) at Gunzip.emit (node:domain:489:12) 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) ``` Personal access token: ``` 2026-07-08T13:07:35:524 [error]: { "userMessage": "Request failed: Can't add GitLab account for https://gitlab.example.com. Check your instance URL and network connection.", "errorMessage": "Invalid response body while trying to fetch https://gitlab.example.com/api/v4/personal_access_tokens/self: Premature close", "stack": [ "FetchError: Invalid response body while trying to fetch https://gitlab.example.com/api/v4/personal_access_tokens/self: Premature close", "\tat Gunzip.<anonymous> (~/.vscode/extensions/gitlab.gitlab-workflow-6.84.2/extension.js:177:332444)", "\tat Gunzip.emit (node:events:521:24)", "\tat Gunzip.emit (node:domain:489:12)", "\tat emitErrorNT (node:internal/streams/destroy:170:8)", "\tat emitErrorCloseNT (node:internal/streams/destroy:129:3)", "\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)" ] } ``` ## What I verified (server side is fine) The same request the extension makes works when done with curl. `/api/v4/user` with a valid PAT over HTTP/1.1 and `Accept-Encoding: gzip` returns `200 OK` with `Content-Encoding: gzip` and `Transfer-Encoding: chunked`, and the gzip body is complete and valid (`gunzip -t` passes). The `glab` CLI also works against the same instance without issues. So the response itself is well formed; only the extension's node-fetch client fails while decompressing it. ## Environment - GitLab Workflow extension: 6.84.2 - VS Code: 1.128.0 (Electron 42.5.0, Node 24.17.0) - OS: macOS (Apple Silicon), Darwin 25.5.0 - GitLab instance: self-managed, 19.1.1-ee, behind nginx ## Likely root cause Node 24.17.0 changed http.Agent keep-alive socket handling ("fix response queue poisoning in http.Agent"), which makes node-fetch v2 emit `ERR_STREAM_PREMATURE_CLOSE` on gzip/chunked responses over reused sockets: [nodejs/node#63989](https://github.com/nodejs/node/issues/63989), [node-fetch#1767](https://github.com/node-fetch/node-fetch/issues/1767). VS Code 1.128.0 is the first release shipping Node 24.17.0, which matches the moment authentication stopped working. A fix on the extension side could be to migrate off node-fetch v2 (e.g. to the built-in fetch/undici) or to disable compression or keep-alive on these requests until the Node regression is resolved.