Syncs failing because of new GitHub limits ?? #534
Comments
jeroen
added a commit
to r-universe-org/sync
that referenced
this issue
Nov 25, 2024
jeroen
added a commit
to r-universe-org/sync
that referenced
this issue
Nov 25, 2024
jeroen
added a commit
to r-universe-org/sync
that referenced
this issue
Nov 25, 2024
jeroen
added a commit
to r-universe-org/sync
that referenced
this issue
Nov 25, 2024
jeroen
added a commit
to r-universe-org/sync
that referenced
this issue
Nov 25, 2024
jeroen
added a commit
to r-universe-org/sync
that referenced
this issue
Nov 25, 2024
|
Updated it to do it in batches of max 1000 and then wait for 60 seconds in between. Let's see if that is more stable... This should only affect |
jeroen
added a commit
to r-universe-org/sync
that referenced
this issue
Nov 25, 2024
|
I think passing the Authorization header has made github happy: r-universe-org/sync@499bc20 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like GitHub has started blocking
git remote lscommands after +/- 5000 calls in a short span.For now his only affects the CRAN sync it seems: https://github.com/r-universe/cran/actions/runs/12010931924/job/33478835990
The text was updated successfully, but these errors were encountered: