Last modified: 2010-05-03 08:49:10 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T25311, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 23311 - Global IP blocks never fully expire (new in 1.16wmf4)
Global IP blocks never fully expire (new in 1.16wmf4)
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
GlobalBlocking (Other open bugs)
unspecified
All All
: Normal normal (vote)
: ---
Assigned To: Andrew Garrett
: code-update-regression
Depends on:
Blocks: 20768
  Show dependency treegraph
 
Reported: 2010-04-24 18:50 UTC by Jesse (Pathoschild)
Modified: 2010-05-03 08:49 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jesse (Pathoschild) 2010-04-24 18:50:24 UTC
When an IP globally blocked with [[m:Special:GlobalBlock]] reaches its expiry date, it stops being enforced but otherwise continues to be active. It is listed as an active block on [[m:Special:GlobalBlockList]], [[Special:GlobalBlock]], and in API results.

I reproduced this by globally blocking 127.0.0.1 for 5 seconds. As of this report 15 minutes later, it's still marked active.
Comment 1 p858snake 2010-04-26 08:24:40 UTC
Based on the title it sounds like this is referring to a regression(/s), tagging as such (+code-update-regression).
Comment 2 Andrew Garrett 2010-05-03 08:49:10 UTC
Those blocks should be purged the next time a global block is made.

I've hidden them from Special:GlobalBlockList in r65840, which can be deployed if necessary.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links