Thu, Apr 6
By looking at that line of code the most likely cause would be that $args happens to be an array of length < 2; but that array is passed by this line of the code and explicitly has size 2. I have a hard time deciphering this.
Mar 19 2017
Confirming it was fixed.
Mar 15 2017
Mar 14 2017
By changing "User rights management" to just "User rights", we will capture the essence of what this page dose for both groups. Hence the patch.
Yes. I am a CU myself, and this information would have helped a lot when we were fighting one of our major vandals in FA WP. That is actually the motivation for all my work on this part of the code.
Mar 13 2017
Mar 8 2017
But why? I think this is a useful feature. We should allow as many easy ways to search UAs as we can.
Mar 7 2017
It is not that the textbox has a width "half the width of fields used further down". It is that it has an absolute width (size=45) as opposed to the next fields which have a relative width (width=100%).
Mar 4 2017
@Umherirrender thanks for clarifying. BloomCache is not an option so we are back to square one.
Mar 2 2017
Mar 1 2017
@jcrespo can you point me out to the part of the code that skips showing the edit log when the user is anonymous and more then X time has passed since deletion? we might be able to re-use some of that logic in https://phabricator.wikimedia.org/T22892 by skipping the query altogether when a page has no logs.
@Umherirrender may I asked what workaround you are talking about? The BloomCache workaround is not possible (all BloomCache related code was later removed as it was only experimental); and the use of partial index page_time that @Springle mentioned above doesn't seem to be sufficient.
I think this is the wrong solution, and the root problem is not the inability to move AFs to new numbers, but the lack of ability to specify the order in which AFs are executed. The fact that they are run based on their ID (first AF1, then AF2, etc.) is just too simplistic.
Feb 28 2017
Feb 24 2017
Feb 23 2017
Feb 20 2017
Interestingly, the abuse_filter_log.afl_filter column (which is effectively a foreign key to abuse_filter.af_id, is not of type bigint. That makes it easy to address this task without DBA involvement (no schema change is needed). I will work on this.
Feb 18 2017
Removing DBA, as the latest patch doesn't introduce any schema changes.
Feb 17 2017
Feb 15 2017
If you want checkboxes on the left of the label, specifically, if you want one checkbox per row followed by a label, the HTMLCheckMatrix is the wrong choice. You should instead use HTMLCheckboxMultiselect. Special:BotPassword was designed based on that wrong choice, and I am working on fixing it.
I think it should; it is yet another example of ignoring the principle of proximity, IMHO.
Feb 13 2017
@Qgil I am retaking this issue, because I think the -2 was not entirely fair. I hope @hoo would revise his review given that an almost identical query is executed every time a delete page is viewed on the wiki anyway.
The checkbox has existed since at least June 2008, and it has been since then always been hard-coded as disabled. I think it would be appropriate to remove it. Patch to follow.
Feb 12 2017
I made the IRC channel ;) If I am not there, it is because I am either not working on any WMF related project (e.g. I am at work, or at a family function) or that I am on such a spotty internet that it cannot even handle IRC.
Feb 11 2017
Feb 7 2017
Feb 6 2017
Rob, I did not get the email. It might have gone into my spam folder which I purged minutes ago. I hope @Quiddity got it though.
Even better, the DIFF should be in the same direction as that on Wiki (as in, JS pages always RTL, content pages based on the content, ...)
Feb 3 2017
@marcmiquel are you done with the clean up? If yes, would you mind closing this task?
Feb 2 2017
Should we add a link to this wall on https://wikitech.wikimedia.org/wiki/Tools_Precise_deprecation ? And should we expand that page to clearly state what it takes to move to Trusty?
For private chats, I created #wikimedia-labs-standards-committee and gave all of you access. It is invite only (you might want to add your cloaks so you don't need to invite yourself).
Feb 1 2017
Jan 29 2017
Jan 28 2017
Log 187152 is not public; if allowed, please post a screenshot.
True. Should we merge this into T155029?
Jan 27 2017
This is not a MediaWiki bug. Tgr's solution perfectly solves the issue; the issue is caused by suboptimal design of a template on that particular wiki.
But if you use those in the original (English) text and it is translatable, then one might incorrectly include them in the translation too, causing problem.
Jan 26 2017
Jan 25 2017
Perhaps merge; not sure in which direction. I believe the CIDR tool should be part of core, with no regard to if and and when we create Special:RangeContributions or not.
The range calculator should be part of core. See T152850
This is very much related to https://www.mediawiki.org/wiki/Requests_for_comment/CheckUser_requirements and T139810