User talk:SQL/AIVAnalysis
Latest comment: 6 years ago by SQL in topic Feature Requests
Bug Squashing
editOpen
editRenames
edit- Bot does not follow renames. SQLQuery me! 22:37, 5 December 2017 (UTC)
Oversighted log entries
edit- Users with oversighted block log entries show up as not blocked. There is no way that I am aware of to get around this. SQLQuery me! 22:27, 5 December 2017 (UTC)
- I have an ugly / hackish workaround for this. Screen-scraping "https://en.wikipedia.org/w/index.php?title=Special:Contributions/" . $username . "&offset=&&limit=1" for "This account is currently blocked" seems to work. These blocks do not show up in API:Blocks, Special:IPBlocklist, nor the Block log - so this was a truly last resort. Running a test case (72's had a few of these) now to confirm. SQLQuery me! 01:23, 6 December 2017 (UTC)
Rangeblocks
editTypos
edit- This report contained a typo; it was corrected a moment later by me, and the account was blocked a few minutes later. It's understandable why your tool didn't pick it up, but maybe a check against case sensitivity if the account tagged at AIV isn't registered?
- This one shows as a never been blocked, but was again a typo. The actual account name was corrected by another editor. This time, I inadvertently left the "e" on the end of "username" in when I selected "usernam" (minus the trailing 'e') for replacing the username. No idea how to account for a typo like that :/ Leave it to a human to really mess things up.
- This one is a special case; I made this request when that account was already blocked; I was asking for a change in the block settings. The bot immediately removed the request, so I then made this request with an intentionally wrong username (adding 'NNN' to the end) so the bot wouldn't immediately remove it. The change in block settings I requested was done [1].
Fixed
editUndefined Index
edit- Occasional "Undefined Index: Compare" on line 53. Need to add a trap to that and see why. SQLQuery me! 01:26, 6 December 2017 (UTC)
Default username
edit- This one was just a typo done by accidentally copy/pasting {{Vandal|username}} per the instructions and not changing "username". Maybe it could ignore "username" as an account name as that is obviously in error. This request immediately preceded the above request, and was done in error. The same text for a request appeared in the next AIV report I made, albeit with the proper username put in.
1= bug
edit- This report resulted in a block of the account. I don't know why your tool didn't pick it up.
- This report resulted in this block. Again, I don't know why your tool didn't pick it up. There was a global lock too; maybe that threw it?
- This report resulted in block. I don't know why your tool didn't find it.
Block timing
edit- At the moment, the script does not check to see WHEN the block happened, just IF it did. At some point, I will probably refactor it to see if the user was blocked within 24 hours of the AIV report. SQLQuery me! 22:40, 5 December 2017 (UTC)
Known issues (cantfix)
editAdding reports from other users
editFeature Requests
editPlanned
editKeywords
edit- Count certain keywords used in reports. I was thinking possibly (feedback would be greatly appreciated!):
- sock, sockpuppet
- block evaision
- promotional
- username
- edit warring
- vandalism