mappjzc opened a new issue, #4592:
URL: https://github.com/apache/incubator-devlake/issues/4592

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   When we try to collect the issue which has more than 10000 issues, we will 
get an error because of the API limit.
   
   
![image](https://user-images.githubusercontent.com/2921251/223126170-cab94690-6d44-402e-998b-33a5e38d9a49.png)
   
   So it makes the task fail.
   
   And then we check over 200 projects and found over 20 projects with 10000+ 
issues.
   
   Someone like Hadoop has more than 100000+ issues total and more than 750000+ 
effort total.
   
   
![image](https://user-images.githubusercontent.com/2921251/223129205-1b74988c-3d68-4717-a27a-98f5c0a51ad8.png)
   
   ### What do you expect to happen
   
   We should better collect all the projects with more than 10000 issues.
   
   And at least, we need to run the other part of the tasks but not fail 
because of this API.
   
   ### How to reproduce
   
   Collect a SonarQube project like Hadoop.
   
   
   
   ### Anything else
   
   It is a good idea to use the createdAfter and createdBefore param. 
   
   
![image](https://user-images.githubusercontent.com/2921251/223134496-712998ba-a57e-46e4-ac49-86833d9649af.png)
   
   
![image](https://user-images.githubusercontent.com/2921251/223137383-e57690cd-1516-47b0-b8db-b6acefc1a588.png)
   
![image](https://user-images.githubusercontent.com/2921251/223137478-81f0a562-1d8d-4da9-a6e4-ed9bc8e242b3.png)
   
   Autotest and check, if it is over 10000, cut the time to be slower.
   
   
   ### Version
   
   main
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to