Skip to content
TORNLIFE More

Dump search

Started by kidkime [2168981] on in Bugs & Issues.

24 replies · 413 views · thread synced · 9 days ago · View on torn.com
About this thread

Posts archived: 25 / 25 posts (100%) · the total is Torn's reply count + the opening post at the last fetch

Counted by TornLife from the archived posts.

Archived posts
25
Discussion span
→
Authority score
62 / 100
Historical score
32 / 100
Story score
49 / 100
Engagement score
68 / 100

People posting, likes and official posts are not counted for this thread yet: on threads longer than one page they come from a periodic pass over the archive, which has not covered it.

Most-liked replies

ChillySpunc [1905415]
LOL, it's been like this since midnight, amazed it's taken this long for a bug report and the response time shows another shit display of event management.
Xiphias [187717]
The server is probably overloaded, but client side it also fails because it's trying to JSON.parse an empty/or null string. Couldn't you test for empty/null response before trying to parse the msg and give a proper error message like "Could not search right now because the lights are out, please try again later" or something, and possibly re-enable the button (after 5 seconds), so you don't have to refresh the whole page to try again.
Chedburn [1] Admin Developer
This would be due the locking method used on the dump, which restricts it to one use at a time (although each use should be very quick). We'll have to find a quick resolution to this.