[Bug][GitHub] GraphQL API gets different data from REST API about incubator-devlake

[klesh]

What kind of data were you collecting? commits? Could you provide more details? It is really hard to understand what was wrong with the current information. I don't know how to reproduce the problem and where to look 😂

[gabrielenosso]

All data related to contributors is different.Yes I was getting commits.You can find the charts with different data in the Components metrics dashboard. Da: "Klesh Wong" ***@***.*** A: "apache/incubator-devlake" ***@***.*** Cc: "Gabriele Nosso" ***@***.***,"Author" ***@***.*** Data: Sat, 27 Apr 2024 19:59:19 -0700 Oggetto: Re: [apache/incubator-devlake] [Bug][GitHub] GraphQL API gets different data from REST API (Issue #7396) What kind of data were you collecting? commits? Could you provide more details? It is really hard to understand what was wrong with the current information. I don't know how to reproduce the problem and where to look 😂 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Startrekzky]

Hi @gabrielenosso , there are many (known or unknown) differences between the results of GitHub's GraphQL or REST APIs. Considering

1. the cost to make them consistent, and the long-term maintenance cost (because the API results change)
2. AND we encourage users to use GraphQL and might not support REST APIs in the future because it's 10x+ slower than GraphQL.

I prefer not changing the status quo here.

[gabrielenosso]

I would also prefer to use GraphQL API.. point is the information I get in Grafana are not from the default branch of the repository... Da: "Louis.z" ***@***.*** A: "apache/incubator-devlake" ***@***.*** Cc: "Gabriele Nosso" ***@***.***,"Mention" ***@***.*** Data: Sun, 28 Apr 2024 03:15:28 -0700 Oggetto: Re: [apache/incubator-devlake] [Bug][GitHub] GraphQL API gets different data from REST API (Issue #7396) Hi @gabrielenosso , there are many (known or unknown) differences between the results of GitHub's GraphQL or REST APIs. Considering the cost to make them consistent, and the long-term maintenance cost (because the API results change) AND we encourage users to use GraphQL and might not support REST APIs in the future because it's 10x+ slower than GraphQL. I prefer not changing the status quo here. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>