dosubot[bot] commented on issue #8187:
URL: 
https://github.com/apache/incubator-devlake/issues/8187#issuecomment-2470442698

   <!-- Greeting -->
   Hello, @kkc-tonywu! I'm here to help you with any bugs, questions, or 
contributions. Let me know how I can assist you while you wait for a human 
maintainer.
   
   <!-- Answer -->
   I found a similar closed issue that might be relevant to your situation: 
[Bug][Gitlab Plugin] Missing `X-Total` and `X-Total-Pages` headers cause data 
losing in gitlab 
plugin](https://github.com/apache/incubator-devlake/issues/4093). This issue 
was closed, and it involved the GitLab plugin handling pagination when certain 
headers are missing 
<sup>[[1]](https://github.com/apache/incubator-devlake/issues/4093)</sup>.
   
   In the current implementation of the GitLab plugin in DevLake, pagination is 
handled by checking the `x-next-page` header. If this header is missing, the 
function assumes there are no more pages to fetch. This means that if both 
`x-total-page` and `x-next-page` headers are missing, the plugin might not 
fetch all available records 
<sup>[[2]](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/api/remote_api.go)</sup>.
   
   Unfortunately, I couldn't find specific logic in the codebase to handle 
cases where GitLab's API returns more than 10,000 records or when both headers 
are missing. You might need to consider implementing a workaround or custom 
logic to handle such scenarios.
   
   
   <!-- Dosu Comment Footer -->
   *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
   


-- 
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: dev-unsubscr...@devlake.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to