SwiftPackageIndex / SwiftPackageIndex-Server

The Swift Package Index is the place to find Swift packages!
https://swiftpackageindex.com
Apache License 2.0
538 stars 42 forks source link

Build triggers failing #3204

Closed finestructure closed 2 months ago

finestructure commented 2 months ago
[ CRITICAL ] requestFailed(500 Internal Server Error, https://gitlab.com/api/v4/projects/19564054/pipelines?status=running&page=1&per_page=100) [component: trigger-builds]
finestructure commented 2 months ago

https://status.gitlab.com

CleanShot 2024-07-10 at 16 51 54@2x

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.

finestructure commented 2 months ago
❯ 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"}
finestructure commented 2 months ago

Project specific:

❯ curl -H "Authorization: Bearer $GITLAB_API_TOKEN" -H "Content-Type: application/json" "https://gitlab.com/api/v4/projects/19427967/pipelines?status=running"
[]⏎
finestructure commented 2 months ago

Also fails with a 500 with a new token.

finestructure commented 2 months ago

https://forum.gitlab.com/t/api-v4-projects-project-id-pipelines-api-call-returns-500-internal-server-error/107441

finestructure commented 2 months ago

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.

finestructure commented 2 months ago

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.

finestructure commented 2 months ago

Seems to have been fixed upstream, thankfully. CleanShot 2024-07-10 at 21 00 44@2x

CleanShot 2024-07-10 at 21 01 06@2x