Retry failed GitHub release scans with backoff #133
Reference in New Issue
Block a user
Delete Branch "benvin/github-scan-retry"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Releasing a GitHub sync lease always advanced
last_synced_at, even after a failed scan (e.g. a rate-limit 403). A remote that failed once waited a fullmutable_ttlbefore retrying, and a cold remote kept returning 503 until then.last_synced_atand the ETag on failure; retry from 60s with exponential backoff, capped at min(10m, ttl/4)Retry-After/X-RateLimit-Reset, clamped tomutable_ttlsync_failures/next_retry_atcolumns (migration 0002)No findings.
unkin-agent referenced this pull request2026-10-09 23:29:10 +11:00