I created a new instance and prepared packaging of xmlrcs to .deb, they can be downloaded here - https://github.com/huggle/XMLRCS/releases/tag/v1.1.0 so deploying XmlRcs is relatively easy now, but there is still some hack needed - that ES client package is no longer in debian repositories, and can be downloaded only using pip, which breaks the packaging system - so right now only redis and xmlrcsd can be installed from .deb packages and works out of the box. es2r which is another essential component must be still installed manually, using venv and systemd unit needs to be slightly modified to load it.

Aha - so that's why it was down, I was wondering, looking through mails, couldn't find anything. Yes that should be easy, I will try to do it soon

I cleaned it up

I would like to point out here that on enwiki due to this change https://en.wikipedia.org/w/index.php?title=Wikipedia:Huggle/Config.yaml&diff=prev&oldid=918980316 Huggle ignores templates older than 3 days. This is very likely reason why Huggle seems to be giving "wrong" warning level templates on English wikipedia. It doesn't see anything that's older than 3 days.

I am just going to close this. The current documentation is imperfect, but it's a wiki, no need to open phab tickets, just go ahead and fix it: https://www.mediawiki.org/wiki/Manual:Huggle/Deploying

This task is done, in order to enable Huggle in write mode, update config page and change read-only to false. I no longer have global editor rights, so I can't do that.

@Xnet1234 Great! so Huggle was enabled, you will see wiktionary when you press Reload on login page.

ok great! do you still want Huggle to be installed there?

I am marking this as declined since there was no update and the project pages are clearly missing - either were deleted or never created.

Hello guys I can see that dawiki is already on the list of project and the config page is also translated, so I think we can close this

Hello, since we couldn't get anyone to vouch for you and especially given that Huggle VPS project is only hosting XmlRcs at this point, which is now fairly stable after latest modifications, I think we can leave this setup unchanged for now. Maybe in the future if the situation changes, I will reach out for you.

I think we can close it, there are too many open issues for Huggle. If there is any specific problem with commons, we should open a task specifically for that

I fixed the missing localizations in https://github.com/huggle/huggle3-qt-lx/commit/9e8858939ce7df6817d77d48cf022f86fb6d95e5

Hello @Xnet1234 is there any update? Are you an administrator of He Wiktionary at least? The consensus is something we need rather for large wikis, if the wiki community is large and you get an approval for installation from at least 1 administrator I think that's enough, otherwise I will have to close this task for inactivity.

Hello @GiorgiOkropiridze is there any update? Are you an administrator of Ka Wikipedia at least? The consensus is something we need rather for large wikis, if the wiki community is large and you get an approval for installation from at least 1 administrator I think that's enough, otherwise I will have to close this task for inactivity.

hello @Nhu_Gay_Me is there any update? Are you an administrator of Cebuano Wikipedia at least? The consensus is something we need rather for large wikis, if the wiki community is large and you get an approval for installation from at least 1 administrator I think that's enough, otherwise I will have to close this task for inactivity.

This was partially fixed in code, but also needs a fix on enwiki configuration. For some reasons, my privileges to edit the configuration pages were revoked (again) and I am kind of tired of bureaucracy involved. So I will just leave a message on feedback page, that update is necessary.

This is fixed here: https://github.com/huggle/huggle3-qt-lx/commit/a2c1868a145254637f77f015c9b7b33af1bd77e3

Merged: https://github.com/huggle/huggle3-qt-lx/commit/83f50e0f1099c024252f7861ecb4d07ad55e6fe3

Thank you for tagging this task with good first task for Wikimedia newcomers!

I tried reproducing this on a test wikipedia, I even synced the local report page and huggle settings with enwp, it however seems to work just fine: https://test.wikipedia.org/w/index.php?title=Wikipedia:Administrator_intervention_against_vandalism&diff=prev&oldid=667053

Hello, this is already possible - open preferences and change preferred provider

as a workaround you can press "o" which opens the page in web browser, where you can immediately see the context, but I agree it's not ideal

I made a fix, but I am on my laptop now, I need a system with multiple screens to test it later: https://github.com/huggle/huggle3-qt-lx/pull/380

hello, I believe this is fixed now

@Anirudh_KK hello, I know this is very confusing, but Huggle isn't hosted on Gerrit, it's instead located on GitHub here: https://github.com/huggle/huggle3-qt-lx

This is trivial to patch, it's just necessary to update the min version in respective CMake files (wherever it's present now) to that <min>...<max> syntax where min stays same as now and 3.5 is set as max (or possibly any newer version of CMake that is works with).

Thank you for tagging this task with good first task for Wikimedia newcomers!

Hello, new version of Huggle was released that contains a patched libirc

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.

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#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.

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.

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

Yes, which operating system?

Hello, I know it's been years, but this was finally partially fixed here https://github.com/huggle/huggle3-qt-lx/commit/887bb8f821ecb8db94235ad11967aaf1c0e1b1d1

I believe it's migrated now

yes it works now

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.

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.

Hello, sorry for the late response, I am far less active these days within the Wikimedia world than I would like to be.

Hello, sorry for the late response, I am far less active these days within the Wikimedia world than I would like to be.

also this

I am trying to follow instructions here - https://wikitech.wikimedia.org/wiki/News/Toolforge_Stretch_deprecation#Move_a_grid_engine_webservice

@dcaro ok but can we somehow check if this URL https://huggle.toolforge.org/ is grid or k8s?

I found this related merge request in Huggle repo - https://github.com/huggle/huggle3-qt-lx/pull/351 where @Se4598 updated the updater URL from / to

I would like to explain what is this being used for right now and confirm that shutdown of this service is not critical for Huggle operation:

I think I added him, but the portal has changed significantly since last time I was doing this, so I am not sure if this is sufficient, he has "reader" permissions. I don't see options to give any more permissions other than full project admin role. Can you please try if you can ssh and use sudo?

fixed - someone started that nohup job while old one was still running, I cleared all running ./es2r.py and it fixed itself.

Hello, the problem was with python script that uses event source and forward data to redis. This event source system is not very reliable (which is one of main reasons why xmlrcs was created so that tools like wm-bot can use that instead of implementing unreliable protocol).

hello, xmlrcs was migrated to xmlrcs2 instance, I kept the old one just in case I forgot anything, but most likely it can be wiped out