This repository was archived by the owner on Jan 19, 2018. It is now read-only.
Multiple problems with issuestats.com #602
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For the past two weeks, issuestats have been having multiple problems with uptime as well as API calls. (even right now at this moment: 03/07/2016 18:13 UTC each page load is more than 3000ms. Do we still want these on our README?
Member
Author
|
It also looks bad when the README.md load and some artifacts are broken :( |
Contributor
|
@cdrage I'm +1. I trust your judgment. |
cdrage
added a commit
that referenced
this pull request
Mar 7, 2016
Multiple problems with issuestats.com
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the past two weeks, issuestats have been having multiple problems
with uptime as well as API calls.
(even right now at this moment: 03/07/2016 18:13 UTC each page load is
more than 3000ms.
Do we still want these on our README?