You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
So GitHub is aware of the problem of not being able to load issue 18. Interestingly, you can load the page if you aren't logged into GitHub. It's mostly a wall of +1's.
@TPS lol, GitHub is not paging comments. I'm so gonna try this out with the comments API.
@dideler@cirosantilli@isaacs Now that #18 is again visible via @github implementing issue-comment-collapsing via 1546 items not shown
View more, can we close this to not further fragment the issue?
Activity
TPS commentedon Mar 11, 2016
@isaacs @cirosantilli @ALL Is there anything you all can do to close #18 in favor of this?
cirosantilli commentedon Mar 11, 2016
@TPS I can't view that either, 500. I'm very curious to what happened to it. Not on wayback machine either.
TPS commentedon Mar 12, 2016
It still officially exists in the listing (https://github.com/isaacs/github/issues?page=19&q=is%3Aissue+is%3Aopen as of right now), but it looks like the 1300 or so 👍 posts killed something on the @github backend, if I had to guess.…
cirosantilli commentedon Mar 12, 2016
@TPS lol, GitHub is not paging comments. I'm so gonna try this out with the comments API.
TPS commentedon Mar 12, 2016
For the record, Github doesn't page most webpages, e.g., https://github.com/cirosantilli?tab=repositories. Is there an issue someplace for that? (#370-ish?) Else, make 1 & move this (off-topic) discussion there?
cirosantilli commentedon Mar 12, 2016
@TPS the repository tabs limits repos, and if you click show all it paginates.
We should make an issue for that, but I'm lazy, feel free to. I'd rather produce an example with an API script first for maximum effect :-)
#370 may have been different, I think the problem was calculating stuff internally, now displaying too much of it. But yeah, similar.
Mottie commentedon Mar 12, 2016
That is interesting... GitHub does collapse very long timelines - see
https://github.com/nodejs/node/pull/5020#issuecomment-178095373.Did anyone report this problem to GitHub?
Mottie commentedon Apr 7, 2016
So GitHub is aware of the problem of not being able to load issue 18. Interestingly, you can load the page if you aren't logged into GitHub. It's mostly a wall of +1's.
TPS commentedon Apr 8, 2016
@dideler @cirosantilli @Mottie I filed #640 (& GitHub response) to fix 1 of #18's root meta-problems. ☺
TPS commentedon May 11, 2016
@dideler @cirosantilli @isaacs Now that #18 is again visible via @github implementing issue-comment-collapsing via 1546 items not shown
View more, can we close this to not further fragment the issue?