Page MenuHomeSoftware Heritage

github.lister: Use Retry-After header when rate limit reached
ClosedPublic

Authored by ardumont on Jan 16 2020, 6:48 PM.

Details

Summary

Following the documentation:
[1] https://developer.github.com/v3/guides/best-practices-for-integrators/#dealing-with-abuse-rate-limits

This does not deal with the concurrency aspect.
For that part, the goal is to deploy the github lister on 1 dedicated worker for now (done puppet side and deployed, worker01 got elected).

Related to T2170

Test Plan

tox

Diff Detail

Repository
rDLS Listers
Branch
master
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 10170
Build 15088: tox-on-jenkinsJenkins
Build 15087: arc lint + arc unit

Event Timeline

ardumont retitled this revision from github.lister: Simplify rate limit approach according to github doc to github.lister: Use Retry-After header when rate limit reached.Jan 17 2020, 10:36 AM
ardumont edited the summary of this revision. (Show Details)
ardumont edited the summary of this revision. (Show Details)
This revision is now accepted and ready to land.Jan 17 2020, 1:49 PM