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
u/Boukert, u/Jobes, and u/Zaebos_11 inadvertently discovered a bug that renders a thread completely inaccessible. The working theory, which they reproduced, is that once a reply chain hits 255 or 256 nested comments the thread locks you out (in other words, you could hit "Parent" 255 times on the final comment and keep going up the thread). Once critical mass is reached, you can no longer view the thread when you try to open it, even though it worked moments earlier. The post can still be seen in the subverse, but will send you to a "Whoops!" page when you try to navigate to the comment section.
The text was updated successfully, but these errors were encountered:
pembo210
changed the title
Post's comments become completely inaccessible with a 256 nested comment section on the comment page.
Post's comments become completely inaccessible when nested comment section containing 256 comments is on the comment page.
Feb 10, 2016
u/Boukert, u/Jobes, and u/Zaebos_11 inadvertently discovered a bug that renders a thread completely inaccessible. The working theory, which they reproduced, is that once a reply chain hits 255 or 256 nested comments the thread locks you out (in other words, you could hit "Parent" 255 times on the final comment and keep going up the thread). Once critical mass is reached, you can no longer view the thread when you try to open it, even though it worked moments earlier. The post can still be seen in the subverse, but will send you to a "Whoops!" page when you try to navigate to the comment section.
Two threads in question:
The comments API fail:
The the post info is still accessible:
/v/bugs post - https://voat.co/v/bugs/comments/850617
Posted on behalf of non-github users.
The text was updated successfully, but these errors were encountered: