429 ratelimiting

Site Feedback
1

First, Thanks for offering this service, I have already setup a a recurring small recurring donation as recommended:).
While configuring my first repos, and adding a own runner I get an 429 in my release flow. I can’t see I do any excessive calls or anything special or extraordinary that should have hammered codefloe to deserve it:) Just regular fetching and quite straightforward builds.

Runner job, https://codefloe.com/l10n-swedish/fri-som-i-frihet/actions/runs/1/jobs/0/attempt/2 (own runner) . So maybe it occurs in own runner setups configs only, which I guess have a fair bit of communication to codefloe, and the HAProxy marks it.

Note: runner

job_level: info

runner:
fetch_interval: 5s
report_interval: 5s

so should not hammer. Added a tmp backoff now , also to get it to work, but I really don’t see I did something weird in the setup and really don’t think it should be needed. So please have a check in the logs.

2

Thanks for reaching out!

Yes, the /api/actions was fully rate-limited by HAProxy until now. CF’s internal runners were not affected as they are fully excempted anyhow - but external runners were.

We’ve now added a custom ACL for this path, which should hopefully resolve this. Let us know if it does or whether you are still rate-limited in some way!

3

Thanks for the prompt fix! Did two runs now without any problems!