Frequent 403 Errors in GitHub Actions – Possible Solutions? #2200
Description
Hello,
I am currently encountering a high number of 403 status codes in GitHub Actions. The jobs take an extremely long time and ultimately fail:
https://github.com/embeddings-benchmark/mteb/actions/runs/13586589565/job/37982824854
https://github.com/embeddings-benchmark/mteb/actions/runs/13591675569/job/37999052862
This is quite frustrating, and finding a solution would be greatly appreciated.
If someone is in contact with Hugging Face and could help address this issue, that would be fantastic. Otherwise, do we have alternative options? Is there general access to the infrastructure of the runners that we could leverage? For example, could deploying a reverse proxy to cache requests help reduce the load on Hugging Face?
Looking forward to any insights.
More:
307 error
https://github.com/embeddings-benchmark/mteb/actions/runs/13587992217/job/37987196418#step:5:183