Hello, I am Petr Bena also known as Petrb (my SUL). I am a volunteer developer working on multiple projects, including Huggle, wm-bot and many others
Fri, Apr 21
Also right now there are filters for both "IP" and "Registered" which is redundant I think
Yes there seem to be some skeleton in the class itself, but the actual code that would make it work is missing
I don't remember, but it's possible, however I fairly sure the configuration wasn't finished otherwise this task wouldn't be still open. I think that warning templates and commons specific configuration is missing.
Wed, Apr 12
Declining a task doesn't solve it.
Sun, Apr 9
Tue, Apr 4
it works to me: https://en.wikipedia.org/wiki/Special:Contributions/Petrb
This commit caused it https://github.com/huggle/huggle3-qt-lx/commit/ebecb24fa4bc8974a0b5c3cdfd5aa4d8cb8382ed
The problem is caused by possible change in revert logic in mainwindow.cpp (I don't know which commit caused this though) it seems that now for some reason we jump to next edit right after call to Revert() and subsequent WarnUser call work with this->CurrentEdit, which in that moment points to next edit in queue (or nullptr in case there is no more).
To reproduce you can revert and warn anything, huggle obviously use next edit as dependency for rollback
It might be also useful if someone could try to identify all users who use this version of huggle (3.2.0) either by scanning the edit summaries or huggle3.css and then notify these users about this issue
Is there any simple step to reproduce this?
Mentioned commit id is irrelevant though could be anywhere from 3.1.21
Fri, Mar 31
Huggle was configured for wikispecies, but I set it to be read only until warning templates for it are created
2e596042ad27 adds this
I removed this string from localization now
Thu, Mar 30
Mar 26 2017
probably some temporary outage of WMF's RCStream
Mar 25 2017
If you want to be able to use $2 you would have to change preferences -> use software rollback
Since f21234e59f07b5a9f61eb75db45e8858a040d3b9 this should work but you will need to use revert-summary-unknown which doesn't support $2 anyway - the reason is that this one is using API rollback and huggle doesn't know to which revision it's going to rollback, mediawiki knows that
that's because WebEngine is implemented in 3.2.0
Mar 23 2017
Well, it would be nice if local community was at least a bit aware, you can start by creating Project:Huggle pages on each of that wiki
Mar 22 2017
@Ciencia_Al_Poder that is a key defined by someone in a channel which you didn't even mention, so whatever channel is that, contact people who have right on bot there and ask them to fix it
Mar 20 2017
and it works... so now it's on your side to finish this
I changed the format of message to
Given that this is meant for devs only I don't really understand why is this localizable
Yes it's an option in Help -> Debug menu, which allows users to switch into "dry mode" which means huggle only pretends to do actions that would change wiki, instead of actually doing them.
btw botbot is 14.04 so it doesn't block stuff
I just nuked wm-bot instance, in project bots. There is one more instance "botbot" that I will look in, maybe there is something I would like to archive for future, and then we can probably nuke whole "bots" project, which is by the way, probably second oldest project of wikimedia labs :)
soo, it seems we are done :)
MariaDB is just as bad as MySQL,
yes that's how it works, first parameter is name of person, rest is a message to deliver. if you want more people and not spam in channel, you can use @notify in private message to wm-bot
so basically, you want a plugin that checks all channel messages for regex /\!ops.*/ and in case message is delivered forward it as a private message to "wmopbot" in a format $sender_nick: $original_message
please keep in mind that wm-bot is also not present in every wikimedia channel, for a list of channels it is currently in, see http://wm-bot.wmflabs.org/db/systemdata.htm
Title of this sounds like some sort of a botporn, but I will have a look
Mar 16 2017
That is 6AM - 8PM EDT
Amazing job Andrew, it seems that it works just fine, XmlRcs was restarted and it works.
Mar 15 2017
probably most easy way to do this would be to switch wm-bot to newly created DB on wm-bot-pg and then start migration of existing data, I will have a look into this later, but I am too busy now. I am not sure if this won't break the sequences though
also I don't see how you could migrate from postgres to mysql online, that also isn't possible, so this definitely would not work.
I am not aware of any such feature and highly doubt it.
@Andrew I tried to reach you on IRC with no luck, can you get to huggle instance? I ran dist-upgrade there and the SSH session timed out and now I can't log back in because LDAP client isn't working there. The upgrade process is running in screen under root user, if you can login there and finish the process it would be great and saved me the time needed to rebuild whole server.
I mean, if huggle-pg is down, wm-bot itself will be still operational, but we lose access to SQL based IRC logs. We probably don't want that, the database is kinda useful and valuable, problem is that migrating to another server is complicated, it's a live SQL database to which new data are added every second, any outage even a second long is a problem here.
wm-bot is depending on huggle-pg instance which was not yet migrated, it's not so easy, it's a postgres database, and it's pretty huge. Hopefully I will be able to resolve this this week, I am extremely busy these days
Mar 7 2017
Yes I will try to upgrade it when I have time
This issue can be close on release of huggle 3.2.0
Mar 6 2017
Don't instances in huggle project host some essential services
Mar 1 2017
Hi, browser is back, also please don't use old "bots.wmflabs.org" domain, it was deprecated some time ago, correct one is wm-bot.wmflabs.org
Hello, yes this is related to both issues, but wm-bot is still logging all channels, just the data are now stored somewhere else, I need to move the web services and merge the log files, should be done soonish
Feb 23 2017
OK I will check that, Huggle was enabled as of now, just click "reload" button in login form and cswiki will be added to list of projects, keep in mind that warning and reverting doesn't work properly yet, so be careful.
Huggle is using warning templates, example can be found here https://en.wikipedia.org/wiki/Template:Huggle on English Wikipedia we use 4 warning levels (usually before user gets blocked). I am not familiar how this works on cs wikipedia, but it's possible to change this for example to 3 levels (I think that's how it works on French wiki).
Please translate https://cs.wikipedia.org/wiki/Wikipedie:Huggle it should contain some basic information about huggle, original version is at [[en:WP:Huggle]]
For record this was requested by Martin Urbanec
Feb 19 2017
There is one problem I need to run identd which requires public IP address, can we get 1 for wm-bot project? Previous bot also had it.
Yes, bot is now up and running on Jessie, I need to test if web hooks work, which is now most important thing, then we need to migrate logs and SQL DB.