HTTP 500 Internal Server Error when trying to Validate CI Config
Checklist
-
I'm using the latest version of the extension (see the latest version in the right column of this page) - Extension version: v4.8.0
-
I'm using the latest VS Code version (find the latest version here) - VS Code version: 1.87.2
-
I'm using a supported version of GitLab (see README for the supported version) - GitLab version: "happens on
gitlab.com
" (16.11.0-pre ca72c9d735a)
- GitLab version: "happens on
Summary
I cannot validate my CI/CD configuration with the command "GitLab: Validate GitLab CI/CD Configuration". When trying to do so, I get the following error notification:
Fetching CI validation from https://gitlab.com/api/v4/projects/1234/ci/lint failed
Steps to reproduce
- Open the
.gitlab-ci.yml
in VS Code - Run the command
GitLab: Validate GitLab CI/CD Configuration
- You get an error message
What is the current bug behavior?
I get the following error notification:
Fetching CI validation from https://gitlab.com/api/v4/projects/1234/ci/lint failed
What is the expected correct behavior?
The CI/CD configuration is validated.
Relevant logs and/or screenshots
2024-04-04T16:10:07:236 [error]: {
"message": "Fetching CI validation from https://gitlab.com/api/v4/projects/1234/ci/lint failed",
"stack": [
"Error: Fetching CI validation from https://gitlab.com/api/v4/projects/1234/ci/lint failed",
"\tat fd (/home/rafael/.vscode/extensions/gitlab.gitlab-workflow-4.8.0/extension.js:493:1470)",
"\tat process.processTicksAndRejections (node:internal/process/task_queues:95:5)",
"\tat async #o (/home/rafael/.vscode/extensions/gitlab.gitlab-workflow-4.8.0/extension.js:493:2540)",
"\tat async VZ (/home/rafael/.vscode/extensions/gitlab.gitlab-workflow-4.8.0/extension.js:567:12827)",
"\tat async /home/rafael/.vscode/extensions/gitlab.gitlab-workflow-4.8.0/extension.js:768:1827",
"\tat async l.h (/snap/code/155/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:150:184831)"
],
"response": {
"status": 500,
"headers": {},
"body": "{\"message\":\"500 Internal Server Error\"}"
}
}
Possible fixes
N/A