Closed finestructure closed 2 months ago
Although the description doesn't look like it'd be related to a 500 from the pipeline call. Trying to reproduce in isolation. It seems to be working in the BuildMonitor app.
❯ curl -H "Authorization: Bearer $GITLAB_API_TOKEN" -H "Content-Type: application/json" "https://gitlab.com/api/v4/projects/19564054/pipelines?status=running"
{"message":"500 Internal Server Error"}
Project specific:
❯ curl -H "Authorization: Bearer $GITLAB_API_TOKEN" -H "Content-Type: application/json" "https://gitlab.com/api/v4/projects/19427967/pipelines?status=running"
[]⏎
Also fails with a 500 with a new token.
The good news is that it seems to be intermittent. We still manage to scheduled jobs sometimes, so hopefully it'll shake itself out upstream at some point.
Interesting, it's the status=running
part that seems to be problematic:
❯ curl -H "Authorization: Bearer $GITLAB_API_TOKEN" -H "Content-Type: application/json" "https://gitlab.com/api/v4/projects/19564054/pipelines?status=pending"
[]
Edit: I just finally managed to make a successful call is all. This clearly doesn't seem to be our problem.
Seems to have been fixed upstream, thankfully.