The Huggle Application itself.
Huggle is a multi-platform application for dealing with vandalism on Wikipedia - Homepage - Code
IRC: #huggle on Libera Chat - https://web.libera.chat/?channel=#huggle
The Huggle Application itself.
Huggle is a multi-platform application for dealing with vandalism on Wikipedia - Homepage - Code
IRC: #huggle on Libera Chat - https://web.libera.chat/?channel=#huggle
One more update: The upstream author (Faidon) of ircstream fixed the underlying bug in https://github.com/paravoid/ircstream/commit/7ef7acea12020189dd450c2de6a91d8baaa18942
Hello, new version of Huggle was released that contains a patched libirc
I tracked down the issue on the Huggle side. The library Huggle uses for IRC (libirc) expects the MYINFO command to have at least 4 parameters, and the new IRC RC server implementation apparently only sends 1. libirc therefore doesn't "autojoin" to channels listed in the IRC server URL, which is how Huggle communicates to libirc which channels to join. The end result is that the RC feed channel is simply never joined.
Hi, I'm receiving this error. I've attempted to regenerate the password, and was able to get through a single edit before receiving this error again.
I captured the conversation between huggle and irc003.wm.o in Wireshark. Huggle connects, sends CAP, USER and NICK, then irc003 sends back a RPL_WELCOME and the MOTD. The MOTD is sent in two packets, and Wireshark complains that the first packet is malformed because it is truncated at the wrong spot:
Internet Relay Chat Response: :irc.wikimedia.org 002 huggle45519553 :Your host is irc.wikimedia.org, running version 1.0+wmf12u1 Prefix: irc.wikimedia.org Command: 002 Command parameters Parameter: huggle45519553 Trailer: Your host is irc.wikimedia.org, running version 1.0+wmf12u1 Response: :irc.wikimedia.org 003 huggle45519553 :This server was created Tue Oct 29 08:55:36 2024 UTC Prefix: irc.wikimedia.org Command: 003 Command parameters Parameter: huggle45519553 Trailer: This server was created Tue Oct 29 08:55:36 2024 UTC Response: :irc.wikimedia.org 004 huggle45519553 :irc.wikimedia.org 1.0+wmf12u1 i bklmtns Prefix: irc.wikimedia.org Command: 004 Command parameters Parameter: huggle45519553 Trailer: irc.wikimedia.org 1.0+wmf12u1 i bklmtns Response: :irc.wikimedia.org 005 huggle45519553 NETWORK=Wikimedia CASEMAPPING=rfc1459 CHANLIMIT=#:2000 CHANMODES=b,k,l,mtns NICKLEN=30 CHANNELLEN=50 CHANTYPES=# PREFIX=(o)@ SAFELIST :are available on this server Prefix: irc.wikimedia.org Command: 005 Command parameters Parameter: huggle45519553 Parameter: NETWORK=Wikimedia Parameter: CASEMAPPING=rfc1459 Parameter: CHANLIMIT=#:2000 Parameter: CHANMODES=b,k,l,mtns Parameter: NICKLEN=30 Parameter: CHANNELLEN=50 Parameter: CHANTYPES=# Parameter: PREFIX=(o)@ Parameter: SAFELIST Trailer: are available on this server Response: :irc.wikimedia.org 221 huggle45519553 +i Prefix: irc.wikimedia.org Command: 221 Command parameters Parameter: huggle45519553 Parameter: +i Response: :irc.wikimedia.org 375 huggle45519553 :- Message of the day - Prefix: irc.wikimedia.org Command: 375 Command parameters Parameter: huggle45519553 Trailer: - Message of the day - Response: :irc.wikimedia.org 372 huggle45519553 :- ******************************************************* Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - ******************************************************* Response: :irc.wikimedia.org 372 huggle45519553 :- This is the Wikimedia RC->IRC gateway Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - This is the Wikimedia RC->IRC gateway Response: :irc.wikimedia.org 372 huggle45519553 :- Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - Response: :irc.wikimedia.org 372 huggle45519553 :- https://wikitech.wikimedia.org/wiki/Irc.wikimedia.org Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - https://wikitech.wikimedia.org/wiki/Irc.wikimedia.org Response: :irc.wikimedia.org 372 huggle45519553 :- ******************************************************* Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - ******************************************************* Response: :irc.wikimedia.org 372 huggle45519553 :- Sending messages to channels is not allowed. Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - Sending messages to channels is not allowed. Response: :irc.wikimedia.org 372 huggle45519553 :- Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - Response: :irc.wikimedia.org 372 huggle45519553 :- A channel exists for all Wikimedia wikis which have been Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - A channel exists for all Wikimedia wikis which have been Response: :irc.wikimedia.org 372 huggle45519553 :- changed since the last time the server was restarted. In Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - changed since the last time the server was restarted. In Response: :irc.wikimedia.org 372 huggle45519553 :- general, the name is just the domain name with the .org Prefix: irc.wikimedia.org Command: 372 Command parameters Parameter: huggle45519553 Trailer: - general, the name is just the domain name with the .org Response: :irc.w [Expert Info (Error/Malformed): Prefix missing ending <space>] [Prefix missing ending <space>] [Severity level: Error] [Group: Malformed]
[09:30:47] <Frakir> Hi, is there a problem with irc.wikimedia.org ? My bot can't connect on this server IRC (or I can't see it with /whois) [09:34:14] --> elukey (~luca@user/elukey) has joined #wikimedia-tech [09:39:54] <volans> Frakir: I can connect fine, it had some changes recently, what error do you see? [09:40:35] <Frakir> On #fr.wikipedia, I see only me and the rc-pmtpa volans [09:40:42] <elukey> o/ also please tell us (if you can, otherwise in pvt) what client are you using and what settings (connection string, port, etc..) so we can try to repro :) [09:43:39] <elukey> Frakir: ahhh yes this is by design, with the new system you have a private sandbox (if we can call it in this way) [09:43:51] <elukey> so you don't see the other bots/clients connected [09:44:04] <elukey> do you see events flowing though? [09:45:02] <Frakir> I have to ctcp chat my bot to act on it, I wonder if I can [09:45:18] <Frakir> I see [10:45:02] <@rc-pmtpa> [[Nate Thurmond]] ! https://fr.wikipedia.org/w/index.php?diff=219819786&oldid=213629315&rcid=533262010 * 2A01:E0A:9F5:C260:BCDB:6A51:322C:1FAF * (+25) /* Records NBA */ resolution homonymie .... [09:46:41] <Frakir> No I can't send ctcp [09:49:03] <elukey> I added a special section to https://wikitech.wikimedia.org/wiki/Irc.wikimedia.org#Why_do_I_see_only_my_nick_and_rc-pmtpa_in_various_channels? [09:49:51] <Frakir> well [09:51:18] <elukey> Frakir: really sorry for this trouble, we tried to track down as many bot owner as possible before the migration but it was a difficult task (we also announced it via wikitech-l etc..) [09:52:12] <Frakir> no problem, it was strange but now it's clear :) [09:52:18] <volans> also please add your bot to https://wikitech.wikimedia.org/wiki/Ircstream#Bots_still_using_the_legacy_setup [09:53:48] <elukey> Frakir: ok thanks!
@Petrb After some further testing, 3.4.12 has not crashed like the way 3.4.13 and Qt6 has. If you don't mind, could I have a Qt5 build of 3.4.13 for testing? Thanks!
Given the two comments from failed attempters above this is clearly not a good first task for whatever reason.
The litany of abandoned attempts in the history shows this is clearly not a good first task for whatever reason.
In case you are unable to build it yourself, here is a build of current master -> https://cloud.bena.rocks/s/qZtXM6QxPbZ3425
I just made changes to build scripts that make it trivial to build Huggle for ARM, even with latest Qt6 framework.
In T310766#10019615, @Petrb wrote:wait, so it crashes no matter if you have to relogin, or only after you use the relogin form? I am trying to understand if they bug was introduced by fix of relogin form, or by shift to Qt6
wait, so it crashes no matter if you have to relogin, or only after you use the relogin form? I am trying to understand if they bug was introduced by fix of relogin form, or by shift to Qt6
In T310766#10016056, @Petrb wrote:In T310766#10012829, @Yoshi24517 wrote:In T310766#10004429, @Petrb wrote:That bug still does trigger from time to time, even in this version, but the relogin form is working now, so while you are going to get a popup informing you about being logged out, you are going to get logged back in, with no need to restart whole huggle. This form normally works automatically, so it becomes just a minor issue.
I did some more testing, because it usually happens when doing the first action that requires editing the wiki in some way. It auto relogs me in, but at some points, Huggle just crashes without explaining why. The most recent crash which I caught, I attempted to revert an edit, Huggle said I was logged out for some reason, relogged me back in, and the app just closed. 3.4.12 never crashed. I checked Event Viewer, and it said Huggle crashed with exception code 0xc0000005.
so, the crash always happens after relogin form? during relogin, or randomly after being re-logged in?
In T310766#10012829, @Yoshi24517 wrote:In T310766#10004429, @Petrb wrote:That bug still does trigger from time to time, even in this version, but the relogin form is working now, so while you are going to get a popup informing you about being logged out, you are going to get logged back in, with no need to restart whole huggle. This form normally works automatically, so it becomes just a minor issue.
I did some more testing, because it usually happens when doing the first action that requires editing the wiki in some way. It auto relogs me in, but at some points, Huggle just crashes without explaining why. The most recent crash which I caught, I attempted to revert an edit, Huggle said I was logged out for some reason, relogged me back in, and the app just closed. 3.4.12 never crashed. I checked Event Viewer, and it said Huggle crashed with exception code 0xc0000005.
In T310766#10016011, @Yoshi24517 wrote:@Petrb : I know its an unrelated issue, but it was brought to my attention in this thread: https://en.wikipedia.org/wiki/Wikipedia_talk:Huggle/Feedback#Automatically_added_to_list_of_users_%E2%80%93_an_unapproved_automated_edit , can we deprecate this? I don't think we need a constantly-updating list of everybody that uses Huggle. It has raised some concerns about it being an unapproved edit, that the user did not manually approve to be done. All semi-automated tools specify that we are responsible for every edit made, and me and Hey man Im josh feel this is no longer necessary. We may have to run an RFC to get consensus first. As of 3.4.13 it still readds you to the list after starting Huggle.
@Petrb : I know its an unrelated issue, but it was brought to my attention in this thread: https://en.wikipedia.org/wiki/Wikipedia_talk:Huggle/Feedback#Automatically_added_to_list_of_users_%E2%80%93_an_unapproved_automated_edit , can we deprecate this? I don't think we need a constantly-updating list of everybody that uses Huggle. It has raised some concerns about it being an unapproved edit, that the user did not manually approve to be done. All semi-automated tools specify that we are responsible for every edit made, and me and Hey man Im josh feel this is no longer necessary. We may have to run an RFC to get consensus first. As of 3.4.13 it still readds you to the list after starting Huggle. Striking unrelated issue
In T310766#10004429, @Petrb wrote:That bug still does trigger from time to time, even in this version, but the relogin form is working now, so while you are going to get a popup informing you about being logged out, you are going to get logged back in, with no need to restart whole huggle. This form normally works automatically, so it becomes just a minor issue.
That bug still does trigger from time to time, even in this version, but the relogin form is working now, so while you are going to get a popup informing you about being logged out, you are going to get logged back in, with no need to restart whole huggle. This form normally works automatically, so it becomes just a minor issue.
Seems to be working fine, the Aborted NeedToken didn't trigger first, so I may need to keep reloading until it happens. No issues with Qt6 build whatsoever when installing.
Possible fix over at T310766, I’m going to test tomorrow but would like others to test as well.
In T310766#10000627, @Petrb wrote:please note this is Qt6 build, regular huggle downloads are all Qt5 based, so let me know if there were any problems related to Qt6 or installation failed, I can try to recreate Qt5 build as well
please note this is Qt6 build, regular huggle downloads are all Qt5 based, so let me know if there were any problems related to Qt6 or installation failed, I can try to recreate Qt5 build as well
I assume Windows 10 x64 or later
In T310766#10000145, @Petrb wrote:Yes, which operating system?
Yes, which operating system?
In T310766#9999483, @Petrb wrote:Hello, I know it's been years, but this was finally partially fixed here https://github.com/huggle/huggle3-qt-lx/commit/887bb8f821ecb8db94235ad11967aaf1c0e1b1d1
the underlying problem with mediawiki API still remains, but at least now the relogin form is working properly for bot passwords as well as for regular passwords
Probably worth mentioning over at T288104 that a possible solution is there, still needs further testing.
Hello, I know it's been years, but this was finally partially fixed here https://github.com/huggle/huggle3-qt-lx/commit/887bb8f821ecb8db94235ad11967aaf1c0e1b1d1
Can this issue be fixed at some point? I'm at 5 relogs with the issue still occurring after each relog, and it is driving me up the wall.
My wikipedia account is https://en.wikipedia.org/wiki/User:Philipnelson99.
Hello, sorry for late response. I don't have any Mac with new ARM based CPUs, so I can't really provide those. Might get my hands on one this year due to laptop rotations in company I work for, will see.
Hi @Petrb, no worries. I thought it might be pretty hard to reproduce, but didn't know if there were any debug options or anything that'd make it easier. I'm using the AUR PKGBUILD of Huggle, as linked above. That uses qt5-multimedia 5.15.12+kde+r2-1 and qt5-webengine 5.15.16-3 if that helps. I don't believe AppArmor or SELinux is interfering. I'm happy to provide a full log, should I just capture the stdout into a file and post it here?
I merged this but hopefully one day we figure some more clean method to do this, maybe Qt has some date parsing function but from what I remember it always worked with OS locale and wasn't easily overriden to match wiki language
Did you check if project options parser-date-prefix and parser-date-suffix aren't able to deal with that? I remember I already implemented some sort of customization for the date parser specifically so that it can be tweaked for non-English projects. I would rather avoid hardcoding any language specifics into the core code.
Full log of huggle startup would help, it always contains the basic info needed for debug.