Sorry -- your subs are gone forever. It's just that they won't ever be killed again.
Sorry again.
Kaylee ,'Shindig'
Do you have problems, concerns, or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Sorry -- your subs are gone forever. It's just that they won't ever be killed again.
Sorry again.
Never mind, I figgered it out. Thanks ita.
I heart the message I got when I tried to post in the closed thread. Cute and nice.
Just like us.
I thought we fixed the thing where people could still post in a thread that hit 10,000.
Yeah, me too. I'm going to have to look into that.
Again, it's a race condition. New posts can arrive concurrently during the time that you're verifiying that your own post # is less than 10000. You can't completely prevent it short of locking the database while you check. Which would slow the board down considerably.
But they didn't really arrive concurrently. 10,005 was posted 13 seconds after 10,000.
New posts can arrive concurrently during the time that you're verifiying that your own post # is less than 10000.
That's not the race, though. As part of the 10000th post going through, the thread header is flagged with "closed." The checking happens when the next post is trying to be written, and if that flag has flipped, no go.
And it used to be much tighter, I swear. The time stamps on those post-10000 posts are pretty far apart.
If that's all taking 13 seconds, something's up somewhere...
And it used to be much tighter, I swear.
It was. I've only seen it go over once since you implemented it, and that was a single extra post.
eta: Okay looking at the closed threads list shows a couple three threads that have an extra post, and the gap on a couple of them is 5 or six seconds.
Does the search function only work on the text of posts? Or is it possible to search for posts by user name?
Experimentation seems to indicate a no on the 2nd question.