If a wiki hasn't seen enough traffic that Block::purgeExpired() is called, it's possible that there are expired blocks plus autoblocks, and when those autoblocks are extended, the expired block will get extended as well.
Description
Description
Details
Details
Related Changes in Gerrit:
Customize query in gerrit
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • demon | T128481 Local block of 114.93.135.192 not expiring on betawikiversity | |||
| Resolved | • demon | T124940 MediaWiki 1.26.3 security release | |||
| Resolved | Legoktm | T128695 Block::updateTimestamp() updates expiry of all blocks for the IP | |||
| Resolved | DannyS712 | T257393 Local block of 180.214.232.49 not expiring on outreach.wikimedia |
Event Timeline
Comment Actions
Change 274623 had a related patch set uploaded (by Legoktm):
Use ipb_id when updating expiry in Block::updateTimestamp()
Comment Actions
Change 274623 merged by jenkins-bot:
Use ipb_id when updating expiry in Block::updateTimestamp()
Comment Actions
Change 304114 had a related patch set uploaded (by Chad):
Use ipb_id when updating expiry in Block::updateTimestamp()
Comment Actions
Change 304115 had a related patch set uploaded (by Chad):
Use ipb_id when updating expiry in Block::updateTimestamp()
Comment Actions
Went ahead and just backported to REL1_23 and REL1_25 so they get caught up in the next release.
Comment Actions
Change 304115 merged by jenkins-bot:
Use ipb_id when updating expiry in Block::updateTimestamp()
Comment Actions
Change 304114 merged by jenkins-bot:
Use ipb_id when updating expiry in Block::updateTimestamp()