Page MenuHomePhabricator

Defect: "blocked" status still displays for users whose block expired
Open, Needs TriagePublic

Description

My block expired on sr.wikipedia.org on July 3, 2017 (17:04 CEST).

However, it is still written "(blocked)" on https://sr.wikipedia.org/w/index.php?title=Special:UserList&limit=1&username=Obsuser, and also on https://tools.wmflabs.org/xtools-ec/?user=Obsuser&project=sr.wikipedia.org there is "Current block: 20170703150424" notice even that current timestamp is 20170714094930 i.e. after this one and that I've been actively contributing with no problems since block expiration.

Event Timeline

Obsuser created this task.Jul 14 2017, 7:49 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 14 2017, 7:49 AM
Obsuser triaged this task as Medium priority.Jul 14 2017, 7:51 AM
Urbanecm lowered the priority of this task from Medium to Lowest.Jul 14 2017, 7:31 PM
Urbanecm added a subscriber: Urbanecm.

Lowest, that isn't anything that can't wait. Also it will require direct database touching probably and this won't be processed. You may ask local sysops to block you and then unblock you (so everything will be processed again), don't know if it will solve anything, just an idea.

OK. I was thinking if this weird thing happens maybe to other accounts too, so that's why triage was set to Normal. I would not like to have block log filled anymore, especially not with unneeded other-purpose-and-temporary blocks; the log already contains two extra rows for when there was block made by mistake (and instantly removed) but also many unjustified ones removed by other admins shortly after being imposed...

This can wait if it's only problem for me but it would be useful to check if anyone else had similar problem on other Wikipedias and what is the cause.

It definitely isn't a issue in the tool itself. Just some Mediawiki internal problem which got replicated to labs.

Bugreporter raised the priority of this task from Lowest to High.Jul 21 2017, 11:09 AM
Bugreporter added a subscriber: Bugreporter.
Aklapper raised the priority of this task from High to Needs Triage.Jul 21 2017, 11:15 AM

@Bugreporter: If you disagree with the urgency/priority of this, replying to the arguments in T170659#3440021 is welcome instead of changing the task priority without providing reasons. "One more affected user" does not make tasks more urgent. :)

I don't see either of those accounts as being marked as (blocked) anymore. Either the bug has been resolved (maybe due to the OOUI upgrade, not sure when that happened) or some layer of caching has cleared.

TBolliger renamed this task from Removing "blocked" status for users whose block expired to Defect: "blocked" status still displays for users whose block expired.Jan 12 2018, 11:10 PM
Bugreporter added a comment.EditedSep 7 2018, 11:02 PM

API also returned (already passed) block status:

https://www.wikidata.org/w/api.php?action=query&list=allusers&aufrom=GZWDer%20(flood)&auprop=blockinfo&aulimit=1

This may confuse other bots and external tools which do not check blockexpiry.