Last modified: 2014-04-07 18:14:25 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 T65552, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63552 - GlobalBlocking isn't properly handling conflicting range block
GlobalBlocking isn't properly handling conflicting range block
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
GlobalBlocking (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-04 23:42 UTC by MF-Warburg
Modified: 2014-04-07 18:14 UTC (History)
3 users (show)

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


Attachments

Description MF-Warburg 2014-04-04 23:42:58 UTC
Apparently the IP range was blocked on Meta already.
Error message below:

    Funktion: GlobalBlocking::insertBlock
    Fehler: 1062 Duplicate entry '190.232.189.0/24-0' for key 'gb_address' (10.64.16.22)
Comment 1 Marius Hoch 2014-04-04 23:45:16 UTC
(In reply to MF-Warburg from comment #0)
> Apparently the IP range was blocked on Meta already.

That shouldn't matter.
Comment 2 Marius Hoch 2014-04-05 01:09:02 UTC
Problem over here (probably) was that you entered a range in a non-normalized form which led to the above error.
Comment 3 Gerrit Notification Bot 2014-04-05 01:10:34 UTC
Change 124041 had a related patch set uploaded by Hoo man:
Check for conflicting blocks after sanitizing the range

https://gerrit.wikimedia.org/r/124041
Comment 4 Gerrit Notification Bot 2014-04-07 17:45:52 UTC
Change 124041 merged by jenkins-bot:
Check for conflicting blocks after sanitizing the range

https://gerrit.wikimedia.org/r/124041

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


Navigation
Links