ipblocks table was missing an index.

Please refrain from opening pointless tasks, this phabricator instance is not for testing.

Hi, what is the purpose for this task?

@MacFan4000 comments? I'm not sure I want to install a brand new extension for testing, however, the only real blocker is doing it (or the task going stale).

@MacFan4000 any objections?

TBH, I'm not sure we really want/need to change it. Unless there is some sort of need for testing that particular toolset.

If there was a consistent issue where there was abuse being stopped by the abuse filters that needed CU information to look into, I'd do it, but there just hasn't been precedent.

Done

Two questions: Why is this task protected? And why not do it through github?

Seems like an upstream issue. I've attempted debugging and testing with another version, but it failed there too.

abusefilter-private gives rights to view the IP of whatever user triggered that filter when viewing an abuse log entry. The intended right may have been abusefilter-view-private (provides ability to view private abuse filters) or abusefilter-log-private (provides ability to view AbuseLog entries of filters marked as private). Either way, anyone with abusefilter-modify (given to sysops) has the ability to view (and modify) all filters (including private).
As such, I've merged the PR; the right does not belong with the oversight toolset.

Done

Any idea what happened to the usual logo though? It was originally located at /var/www/html/resources/assets/logo.png

Functionality now added, you can use either of $log comments or $sal comments, and whatever comments is will be added to the page. (This will take a minute even after the bot responds in the IRC channel.)

Ugh, I was just in the process of launching Void-bot with the added functionality when this issue came up again. I'll have to bypass the need for login, or something.

All I have to do is work the script into the bot and then deploy it. This will take a bit of fiddling, since the file structure where I host the bot is significantly different from where I've been testing it. (And I also need to make sure I can install Pywikibot there properly).

I've gotten far enough that I can do this using a custom pywikibot script. I now just need to make the java bot call the pwb script, modify a text file, and then call another pwb script. Shouldn't take too long now.

There's no real need for adding additional rights. Requesting existing rights should be done on wiki.

I've got free time today to do testing. I needed to figure a way to get the python scripts to interact with the java framework, and I believe I have a solution.

I'm having trouble getting the script to accept the site's cert. It keeps throwing unable to find valid certification path to requested target

Done, and added MacFan4000 as admin (I think)

I'll handle it when in around four hours.

I've encountered an unexpected error while attempting to test. I might have the fix done soon, but I can no longer give a good estimate on how long it will take to finish.

I'll get to work on it tomorrow. Should be up and running by the weekend.