using the api to migrate a gitlab repo is triggering "secondary rate limit"

[mattip]

Checklist

• I checked all open bugs and none of them matched my problem.

Environment

• https://api.github.com
• GitHub Enterprise Server:
• GitHub Enterprise Cloud
• Node.js
• Browsers:
• Others:

Versions

@octokit/rest@18.0.0

What happened?

When using https://github.com/piceaTech/node-gitlab-2-github to convert a gitlab repo to github, I am getting an error

RequestError [HttpError]: You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later.

The package waits 2 seconds between API calls, and checks the X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset fields.

The source repo has over 3000 issues, many with valid @user references. I am migrating it to a private personal repo to prevent sending notifications to team members.

This seems to happen after creating 30 issues.

Minimal test case to reproduce the problem

What did you expect to happen?

I expected to be able to create more than 30 issues in an hour.

xref piceaTech/node-gitlab-2-github#28

[mattip]

Could it be there is a non-documented limit on creating more than 40 issues per hour?

[mattip]

... now it is down to 25 issues / hour

[wolfy1339]

I'm sorry to hear that you're having issues with throttling. I'm not very familiar with the codebase and the REST API, so unfortunately I can't really be of any help.

Unfortunately the JS @octokit packages currently have no active maintainer.

You can subscribe to this discussion for any further updates.

[mattip]

So sorry to hear. The discussion you linked to is locked, so I cannot subscribe.