Open jzf2101 opened 9 years ago
Both issues are the same. When we make the request the first time, GitHub needs a bit of time to process the data, so it sends us an empty response with a 202 status code. To actually get the results, we have to send the request again. Basically we need to check for that 202 code and retry in N ms if we get it, maybe a few times before giving up. For now you should be able to get the data to work by refreshing shortly after you request the first time
On Wed, Mar 25, 2015 at 4:09 PM, jzf2101 notifications@github.com wrote:
My chart thinks this repo is 100% of the data, but that can't be right based on the size of my other repos:
[image: screen shot 2015-03-25 at 16 07 55] https://cloud.githubusercontent.com/assets/1373035/6834272/498eee08-d309-11e4-8e12-f9b17cb0fc27.png
— Reply to this email directly or view it on GitHub https://github.com/blanksblanks/project-cookie/issues/33.
@ozzieba Both issues are the same? Which issue are you referencing
I meant #33 and #34. I may be wrong, but that problem could certainly cause both issues
On Wed, Mar 25, 2015 at 4:27 PM, jzf2101 notifications@github.com wrote:
Both issues are the same? Which issue are you referencing
— Reply to this email directly or view it on GitHub https://github.com/blanksblanks/project-cookie/issues/33#issuecomment-86203282 .
My chart thinks this repo is 100% of the data, but that can't be right based on the size of my other repos: