Posting to a topic as it is autoclosing appears to trigger 502 and 504 errors
-
It has been observed 2 or 3 times today that 502 and 504 errors occur as a topic is being automatically closed by @system. In at least two of those, someone was attempting to post as it was closing. It is uncertain whether this is a necessary condition, or just the autoclosing by itself is sufficient to trigger the errors.
Still getting errors trying to post this 13 minutes after the topic closed, except that it didn't because @loopback0 just posted in it. What???
-
I tried to post as the thread we were testing in was closing, FYI
-
as did i.
had to abandon because 403 error after the site finally came back.
-
I was, too, and so was @loopback0, apparently.
-
except that it didn't because @loopback0 just posted in it.
I can post in closed topics (TL4) so I guess the post just stuck after the topic closed.
-
isn't @loopback0 TL4? He can post in any topic regardless of closure....
Filed Under: I also wanted to post in that topic :D
Addendum: Freaking
@loopback0Hanzo
-
So, posting to a thread (a normal forum action) while locking a topic (a normal forum action) brings Discourse to its knees for about 15 minutes.
-
So it was you bastards messing with my testing! Curse upon you and your build servers!
On a more serious note, this probably warrants some testing in a more isolated environment. Thinking @riking's test server perhaps if he agrees?
-
-
-
Thinking @riking's test server perhaps if he agrees?
Mine's around. http://pjh.homeip.net/
-
-
My subjective viewpoint:
Whee, this is fun... Why did the countdown go away?
HardwareGeek posts about 30 seconds remaining
.Lol discotime. Maybe I can post an inb4... oh but this category doesn't count for badges...
Two more posts happen
Lol screw it.
I post. HardwareGeek posts.
I reload the page and it starts spinning forever.
Damn. I guess it's true.
The page comes back up... but isn't locked. I attempt to post "Guess that's confirmed" or some such. The site crashes entirely, with a big white 504 page.
Ohgod I broke it >.>
The site comes back up! And the thread is locked.
Awesome. I'll file a bug report...
There are three bug reports.
-
I was about 30 seconds away from bug report #4 before I saw the notifications spring to life
-
You have a bug report.
You use Discourse
You now have 3 Bugreports, a broken Forum and an appreciation for RegexFiled Under: probably not the regex thing... but whatever
-
For completeness, putting here too.
-
On a more serious note, this probably warrants some testing in a more isolated environment. Thinking
@riking's test servermeta.dFTFY.
Also, how the hell does that even happen.
-
-
I kind of love that one of the most serious downtimes of Discourse was indeed not caused by bots, or people trying to break it but by moderation in form of closing topics...
It's like, why would we even be trying anymore...Filed Under: we should stop moving topics and renaming stuff... I am scared of what might happen
-
Thinking @riking's test server perhaps if he agrees?
No cooties triggered there, just tried it.
-
-
...My avatar is gone:
Hard reload brought it back
-
but by moderation in form of closing topics...
I didn't even want to be right on that theory, either.
-
Discourse.
No. No, no, no. Hold on.
I get it that Discourse is buggy. Shit happens. But the bugs we're getting are things that shouldn't even have the slightest connection. Things like "server uptime" and "closing topics" are in two totally different realms. It's one thing to have a bug like "when you vote in a poll, it doesn't register" - that makes sense. But that's like "when you vote in a poll, your avatar disappears". TDEMSYR.
So either you've found causality where there's only correlation, or holy mother of fuck.
-
So either you've found causality where there's only correlation, or holy mother of fuck.
I'm gonna go with the second clause of your sentence.
-
I'm gonna go with the second clause of your sentence.
i'd open another autoclosing topic to prove the correlation but i don't want to be blamed for another downtime.
-
Might be the better call right now:
Why does this not onebox??
Filed Under: Wait until they figured out what
they were doingis going on
-
It's odd - end the URL with /5 and it does, but /6 and it doesn't.
Quoted, instead.
@sam said:This is super odd @codinghorror we are also seeing this on BBS and bbs has the "auto closure" in common with WTF.
I am going to dig in to this code now.
-
It's odd - end the URL with /5 and it does, but /6 and it doesn't.
Another bug! @discoursebot
-
@HardwareGeek - Last Day Without A Discourse Bug: null
-
It works over at meta, btw... this is really weird....
Filed Under: Oh well, thats a bug for another day, I guess... but we might as well page @Sam
Addendum: Aw, come on @HardwareGeek, you just had to Hanzo me here?
-
Aw, come on @HardwareGeek, you just had to Hanzo me here?
-
FTFY.
Good luck finding an auto-closing topic over there...
But the bugs we're getting are things that shouldn't even have the slightest connection.
I can't think of what you mean.
https://meta.discourse.org/t/polls-cannot-be-closed-if-allow-user-locale-is-enabled/24247
-
all these auto-closing topics are killing the server again. i can't "read" anything because the mark as read flag is timing out...
-
Sam's looking into it at the moment.