/stats/contributors never returns a response, only HTTP status code 202 forever #192970
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
API
Body
The
/repos/{owner}/{repo}/stats/contributorsAPI endpoint is broken.This endpoint is supposed to return an empty response with an HTTP 202 status code until a background job has computed aggregate statistics, at which point the endpoint returns the data and an HTTP 200 status code on the subsequent request. Instead, as of a few days ago, it returns 202 forever, and never returns a 200 with the data. The endpoint currently misbehaves this way with every repository I have tested. This API failure started sometime between April 12 and April 13.
I maintain a modestly popular project to generate GitHub statistics images, which uses this API. One of the key statistics (lines of code changed) is broken for every user until this problem is fixed.
I noticed that the contributors page for each repo now requests a non-API endpoint to get the same data (
https://github.com/jstrieb/github-stats/graphs/contributors-data). That new path has a similar pattern of returning 202, then eventually returning data, and the returned data has similar schema to the original stats endpoint. The new page doesn't seem to have reliability issues, but is also not a documented API for accessing this data. As an API consumer, it's frustrating that the data is still clearly available, just not to me.There is nothing in the GitHub blog "changelog" mentioning adjustments to the behavior of this API, nor is there any information about a breaking change on the API documentation page for such changes. There is likewise no mention of this bug in the product roadmap. That leads me to believe that this is an unintended bug.
Possible duplicate of #192571.
Beta Was this translation helpful? Give feedback.
All reactions