Unexpected Gitlab Runner Failure from Rate Limiting
Someone please tell @anarcat there is problem with my Gitlab Runner.
The Gitlab runner's request to gitlab container registry get rate limited by Gitlab's rate limiter! (I will have difficulty reading this sentence >~<)
When it successfully failed: https://gitlab.torproject.org/shelikhoo/webtunnel/-/jobs/1060903 (archived: https://archive.is/9fx6u)
When it successfully miscalculated: https://gitlab.torproject.org/shelikhoo/webtunnel/-/jobs/1060881 (archived: https://archive.ph/wip/La2rf )
And then failed successfully: https://gitlab.torproject.org/shelikhoo/webtunnel/-/jobs/1060882 (archived: https://archive.ph/wip/OSH8W)
Steps to reproduce
- Go to https://gitlab.torproject.org/shelikhoo/webtunnel/-/jobs/1060923
- Click medium square blue retry button on the top right of the page. (you are authorized to use your sudoer impersonate entitlement to login into my account to try this if necessary. What?! you need my password to login into my account? my password is
*********) - watch it fail again.
What is the current bug behavior?
Runner assigned to shelikhoo/webtunnel is unable to pull from gitlab container registry dependency proxy.
What is the expected correct behavior?
Gitlab runner for shelikhoo/webtunnel operates without runner system failure.
When did this start?
(Sorry I don't know, I just begin to update webtunnel repo to use dependency proxy today.)
Relevant logs and/or screenshots
(See also: https://gitlab.torproject.org/tpo/tpa/team/-/issues/42152, restricted page)