'Filter by status' broken

I blame the DB replication patches. I looked at the page and the account you were talking about isn't showing up as queued anymore. This worked fine for ages, but ever since the replication patches hit d.o, there have been strange and subtle bugs like this, caused by delays between when the primary DB is updated, and when those changes are replicated to the secondary read-only DB(s). Therefore, I'm moving this into the infra queue. I'm tempted to mark this 'closed', since I doubt anyone's going to do anything about it, but I figured I should at least give folks a chance to see it and comment/won't fix/close whatever.

Is the page using a pager query? then yes, this might be replication related. If it is not, then this is unlikely.

it is likely more specific than the replication patch. this is a symptom of replication delay which is a data center problem and not really a code problem. kinda spliting hairs though. once our slave server stabilizes it will consistenly take seconds for data to replicate and this becomes a non issue.

@killes: Yes, it uses a pager query.
@moshe: Right, that's why I moved this into the infra queue, not core.

cheers,
-derek

Well, the problem is quite simple to explain. AjK approved two accounts. This information gets written to the master and propagated to the slave. But the pager query for the new form immediately got to the slave and was answerd from the not-yet-updated data there. What we need in these cases (forms on paged pages) is a way to tell the paged query to go to the master instead of the slave. The watchdog pages and the "admin content" area are further canditates for this.

Does this issue still need to be fixed?