[VS Code] [Spike] Self-signed certificate failure
Checklist
-
I'm using the latest version of the extension (see the latest version in the right column of this page) - Extension version: Put your extension version here
-
I'm using the latest VS Code version (find the latest version here) - VS Code version: Put your VS Code version here
-
I'm using a supported version of GitLab (see README for the supported version) - GitLab version: 17.4
Summary
The GitLab extension doesn't work because it can't communicate with the API because we used a self-signed certificate. The Ignore Certificate Errors setting is on.
Steps to reproduce
- Update VS Code for the September update
- GitLab is broken! (v5.15.0)
What is the current bug behavior?
The following error is thrown:
What is the expected correct behavior?
Should work properly and follow the ignore SSL errors.
Relevant logs and/or screenshots
2024-10-04T12:16:21:458 [error]: request to https://gitlab.companyname.local/api/graphql failed, reason: self-signed certificate
FetchError: request to https://gitlab.companyname.local/api/graphql failed, reason: self-signed certificate
at ClientRequest.<anonymous> (/home/mvine/.vscode-server/extensions/gitlab.gitlab-workflow-5.15.0/extension.js:204:436579)
at ClientRequest.emit (node:events:519:28)
at TLSSocket.socketErrorListener (node:_http_client:500:9)
at TLSSocket.emit (node:events:519:28)
at emitErrorNT (node:internal/streams/destroy:169:8)
at emitErrorCloseNT (node:internal/streams/destroy:128:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Possible fixes
Unknown
Edited by Kisha Mavryck Richardson

