klesh commented on issue #7510: URL: https://github.com/apache/incubator-devlake/issues/7510#issuecomment-2753679150
Silly me, I somehow thought it was gitlab when I reproduced the problem. Sorry about that. As of github graphql, this is a known issue and currently doesn't have a good solution due to: 1. We have to make sure the order of issues is consistent when fetching data page by page, or it might end up with corrupted or incomplete data, thus, we must order them by `CREATED_AT` when fetching. 2. It works fine for gitlab because it supports filtering by `UPDATE_AT` while ordering by `CREATED_AT`. Unfortunately, Github Graphql doesn't support such a filtering, not that I know of. I just checked [Forming calls with GraphQL - GitHub Docs](https://docs.github.com/en/graphql/guides/forming-calls-with-graphql) and still can't find the required filtering parameter. It is a shame, and it can only be fixed by launching a full refresh. Let me know if I missed anything. -- 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
