Why is Status thread locked?
-
The title says it all, really. Why is the Official Status Thread locked?
Oops, meant this to be in Meta, not Bugs. Whatever...
-
because is occurring.
-
Mods are asleep, post status in here
-
@tsaukpaetra Locking it was . would have been to do nothing. And why no explanation.
-
and the necessity to act immediately, likely on mobile. Though what exactly in there required immediate action is unclear to me as well.
-
Mods like to lock threads during a jeffing to make sure that no new posts that should be jeffed get posted while the jeffing is jeffing its way through the thread, resulting in need to do additional jeffing when such posts are discovered.
-
@pleegwat said in Why is Status thread locked?:
Though what exactly in there required immediate action is unclear to me as well.
It was simply to stop other people replying while I was trying to fork the topic.
Emphasis on trying there. Three times.
-
@anotherusername That makes sense, although quite at a loss to see what might have needed jeffing. It's not like the Status thread could have OT posts, since it has less of a defined topic than anything else here. And I didn't see anything that could lead toward a flame war, much less an actual war that needed to be quashed. PII, maybe, but that would probably only need jeffing 1 or 2 posts, I would think, so not need locking.
-
@hardwaregeek said in Why is Status thread locked?:
That makes sense, although quite at a loss to see what might have needed jeffing.
It was the conversation going on about temperature.
Status
tends to be for one-post things with maybe one or two replies. Which most ignore.If a decent conversation springs up, it sometimes makes sense to break it out to give it a wider audience.
-
@hardwaregeek said in Why is Status thread locked?:
Oops, meant this to be in Meta, not Bugs. Whatever...
I'll move it.
-
@pjh said in Why is Status thread locked?:
@pleegwat said in Why is Status thread locked?:
Though what exactly in there required immediate action is unclear to me as well.
It was simply to stop other people replying while I was trying to fork the topic.
Emphasis on trying there. Three times.
When you're done, can you merge in the topic I just created wherever's appropriate?
-
-
@pjh said in Why is Status thread locked?:
@hardwaregeek said in Why is Status thread locked?:
Oops, meant this to be in Meta, not Bugs. Whatever...
I'll move it.
That was interesting. First time I've ever seen a topic move while I was reading it. Surprisingly, the behavior was actually fairly sane and didn't break anything. It didn't even lose my last-read marker; although the page reloaded at post #1, the return-to-last-read toaster did just what it says on the tin.
-
@pjh said in Why is Status thread locked?:
@gÄ…ska said in Why is Status thread locked?:
When you're done
I gave up.
-
@hardwaregeek said in Why is Status thread locked?:
@pjh said in Why is Status thread locked?:
@gÄ…ska said in Why is Status thread locked?:
When you're done
I gave up.
As I pointed out in
Bugs
- that's exactly what the servers did. Each time I tried.
-
@pjh said in Why is Status thread locked?:
Emphasis on trying there. Three times.
Ah, yes, that would explain this:
-
@administators should I just kill watchdog.bash? Has it done a single helpful restart recently?
-
@ben_lubar said in Why is Status thread locked?:
@administators should I just kill watchdog.bash? Has it done a single helpful restart recently?
My main concern is why should a process forking a topic cause itself to be targeted in such a manner? i.e. should it really take so long?
-
@pjh said in Why is Status thread locked?:
My main concern is why should a process forking a topic cause itself to be targeted in such a manner? i.e. should it really take so long?
I believe that there was a performance issue identified and fixed but not yet released.
@ben_lubar said in Why is Status thread locked?:
@administators should I just kill watchdog.bash? Has it done a single helpful restart recently?
Let's try that. We haven't (knock on wood) had a lot of restarts aside from those that have been self inflicted. I suppose if it's a problem we could turn it back on.
-
@pjh Yeah, how difficult can it possibly be to
UPDATE POSTS SET TOPIC =
...Oh, wait. NoSQL.
-
@masonwheeler The slowdown was previously related to updating everyone's bookmarks, which is tricky since different people's bookmarks are different. I forget what the problem was this time.
-
@boomzilla Oh, is that a thing now? Previously it seems that forked topics simply don't give you any bookmark; you get stuck at the beginning of the topic no matter how far into the forked material you've read.
-
@masonwheeler No, I was referring to updating your bookmark in the original topic. When we started with nodebb, it wouldn't update at all, so a large jeffing would leave people with bad bookmarks until the topic caught up to the old size. I made a fix for that, but using
async.map
or something I managed to blow out the RAM for a sufficiently large or popular topic (or something like that). That got fixed a while ago, but there's something else going on with forking a big topic.I think there's a bug thread somewhere. Or maybe it's in the nodebb updates topic.
-
@boomzilla Ah, I see. That makes more sense.
-
@boomzilla said in Why is Status thread locked?:
@pjh said in Why is Status thread locked?:
My main concern is why should a process forking a topic cause itself to be targeted in such a manner? i.e. should it really take so long?
I believe that there was a performance issue identified and fixed but not yet released.
@ben_lubar said in Why is Status thread locked?:
@administators should I just kill watchdog.bash? Has it done a single helpful restart recently?
Let's try that. We haven't (knock on wood) had a lot of restarts aside from those that have been self inflicted. I suppose if it's a problem we could turn it back on.
To turn off watchdog.bash,
docker exec wtdwtf-nodebb killall watchdog.bash
To turn it back on,
docker exec wtdwtf-nodebb bash -c './watchdog.bash &'
-
@hardwaregeek said in Why is Status thread locked?:
@tsaukpaetra Locking it was . would have been to do nothing. And why no explanation.
Can someone explain this kneeling warthog meme? Google didn't help.
-
@sockpuppet7
The root meme: https://what.thedailywtf.com/topic/11847/the-official-likes-topic/66908Edit: Basically, around the time that the NFL kneeling protests were getting a bunch of attention again, @boomzilla posted a kneeling warthog in protest of being accused of doing work, and that's kind of morphed into mods protesting being made to do work (or plebs joking about mods' protests when made to do work).
-
@izzion Also inspired by Salon floof taxes.
-
I think I may have found it: https://github.com/NodeBB/NodeBB/blob/e99d4a5c612a3ad3841364081a8367187c2276cf/src/topics/bookmarks.js#L60
All it does is load the entire list of post IDs in the topic for every user that's ever read the topic, up to 50 times concurrently. How could that possibly be a problem?
-
@ben_lubar node is async so this shouldn't cause a performance problem.
-
@bb36e
Every time I have to deal with threading, I get asyncing feeling.
-
-