"Abuse detected" slowdowns and possible solution

[DavidGriffith]

I have a fairly small repo with 229 issues that gets stalled around Issue 40 with the following message:

Migrating issue #40 ('[PLACEHOLDER] - for issue #40')...
Abuse detected for request POST /repos/{owner}/{repo}/issues
Retrying after 1000 seconds!

At this point I can leave it running for hours and it won't ever finish. Is there some way I can throttle back API usage or avoid this some other way? Stopping and restarting doesn't help as it 1) starts from the beginning again and 2) I hit the "Abuse detected" immediately. This has a side-effect of ticking off Github such that when I try to file an issue, it is rejected with There was an error creating your Issue: was submitted too quickly.

[DavidGriffith]

Putting a quick-and-dirty delay of ten seconds at the beginning of the for loop in transferIssues() seems to allow the transfer to take place without provoking Github's abuse-detector. I'm not sure what the shortest acceptable delay is -- hopefully a lot less because transferring https://github.com/DavidGriffith/minipro-import-test from Gitlab took a couple hours. Is simply sticking in a delay the right way to do this? If so, I'll polish this fix up and submit a pull request.

[klausmcm]

@DavidGriffith Could you please share a copy or at least a diff of your transferIssues() function with the delay? There are two for loops in that function. I guess the second loop is where the delay is?

[mschoettle]

In my transfer of merge requests I am currently up to 20 seconds. I tested 10 and 15 which was not sufficient.

Diff: mschoettle@8898ba2

[mschoettle]

Actually, 20 seconds also wasn't enough. I suspect that it is related to how many comments are added to the PR.

So maybe the 2s delay in between creation is not sufficient.

[NetSysFire]

I have tried @mschoettle's patch with a 259 issues repo I have just migrated and I have gotten no "abuse detected" slowdown. Everything worked pretty well.

[mschoettle]

#226 should hopefully fix this. It needed an upgrade to plugin-throttling with the latest best practices in avoiding rate limit.