Ok, who broke One Post?
-
I sense a distinct lack of countdown...
-
And here.
Wasn't me.
-
Or seemingly any topic since this one:
-
@PJH - any ideas? Anything obvious in a log file? Has it reset a Discosetting or something?
-
Yeah...only @PJH or similar would have that power.
-
Paging lords of accessing the shitty admin UI, @PJH and @boomzilla.
-
I sense a distinct lack of countdown...
Hmmm.. Something happened 5 hrs ago it seems (1315 UTC.)
... And looking at whose post was the first to break, I think I know what may have caused it...
@sam?
-
Don't look at me, I can only do retail abuse of UI around here.
-
Did you find a magic GUID that breaks Discourse?
Well, when I say magic...
-
Knowns:
- A manually closed topic is a staff-coloured post attributed to the person (TL4+) closing it
- An automatically closed topic is a staff-coloured post attributed to
- The person (TL4+) if the close time is modified
- The opener if they are TL4+
- @system if they're not.
What happened there
- The opener was Admin when the post was created
- Before the auto-close happened, the opener was relegated back to TL0
Assumption
- Since the opener (who'd normally close the topic) was no longer TL4+ sidekiq is having a hissy fit on that post, and is refusing to close any others after it.
-
Was it that @PJH_0 guy? That guy is a troll I am telling you! He even posted in the Lounge and everything!
Filed Under: Apparently he is only here to download his own posts. What a narcist!
-
So basically you broke Discourse forever by using its features in the intended way.
-
That sounds reasonable-ish. But...does sidekiq actually set the auto-close, too?
-
I'm guessing that the user who is to close the topic is set when [topic created|autoclose changed] then when the time comes, that user is used to close it later.
If that user loses the privilege by then it seems to cause a problem.
I'm making an ass-u-me-umption that it's sidekiq with the problem, with that, but I think I've figured the underlying problem.
-
but I think I've figured the underlying problem.
That they don't have a catch for it to fall back to @system closing the topic if the user can't at the time of the auto-close?
-
You must be new here.
-
Ah, right.
We're Doing It Wrong™.
-
That they don't have a catch for it to fall back to @system closing the topic if the user can't at the time of the auto-close?
More or less, yes.
-
I'm making an ass-u-me-umption that it's sidekiq with the problem, with that, but I think I've figured the underlying problem.
Sounds like something for meta.d plus maybe they will be able to confirm or deny your assumption.
-
Seems to have closed some posts after an hour anyway?
EG http://what.thedailywtf.com/t/crap-didnt-work-either/37109/4
-
Yeah - with the exception of @PJH_0's post, it seems the message at the bottom is missing but the Auto Close is otherwise working.
-
FIX: Don't fail topic auto-close if privledges are lost by riking · Pull Request #3303 · discourse/discourse