User talk:Xqt

#8661
Hi, Xqt. Please take a look at my comment on Special:Code/pywikipedia/8661. Best regards, Malafaya 12:09, 24 October 2010 (UTC)
 * Done by Multichil. Thanks, Malafaya 12:19, 24 October 2010 (UTC)

archivebot.py — Does it works for "es"-projects?
Hello Xqt. May I know if the archivebot.py script works for Spanish-language projects? In the past it didn't due to timestamp-related things IIRC. If it isn't yet supported, I can pass you the required changes if needed so you can push them to the pywiki scripts (if you like, of course). Thank you, --Marco Aurelio (talk &bull; meta) 19:58, 8 May 2012 (UTC)
 * I've never tried it. If you have a patch for currently used timestamps, that would be great. Xqt (talk) 05:34, 9 May 2012 (UTC)
 * I did tested it yesterday and it gives me an error message telling me that the spanish language is not currently supported. I can submit the required changes but I need to know which needs to be translated or addapted. Regards. --Marco Aurelio (talk &bull; meta) 14:07, 9 May 2012 (UTC)
 * Could you give us the error messages and traceback at sourceforge. I cannot follow. Xqt (talk) 16:50, 9 May 2012 (UTC)

Bug
Your edit -- http://svn.wikimedia.org/viewvc/pywikipedia/trunk/pywikipedia/category_redirect.py?r1=9692&r2=10485 seems making it not working when I edit Wikimedia Commons. --Zhuyifei1999 (talk) 11:38, 31 May 2013 (UTC)
 * Sorry, this is an inapropriate bug report. Please give us more information about this issue, e.g. the traceback, your command line and the output of version.py. Btw you may use our bug tracker at sourceforge to report these details. Xqt (talk) 05:05, 1 June 2013 (UTC)

yifei@ubuntu:~/pywikipedia$ python category_redirect.py No handlers could be found for logger "pywiki" WARNING: Your account on commons:commons does not have a bot flag. Its edits will be visible in the recent changes and it may get blocked. Getting 2 pages from commons:commons... Done checking hard-redirect category pages. Traceback (most recent call last): File "category_redirect.py", line 579, in    main File "category_redirect.py", line 574, in main bot.run File "category_redirect.py", line 409, in run prop='info|categoryinfo'): File "category_redirect.py", line 266, in query_results    querydata.update(result['query-continue'][query_type]) NameError: global name 'query_type' is not defined yifei@ubuntu:~/pywikipedia$ python version.py Pywikipedia [http] trunk/pywikipedia (r11514, 2013/05/09, 16:42:02, OUTDATED) Python 2.7.3 (default, Aug  1 2012, 05:16:07) [GCC 4.6.3] config-settings: use_api = True use_api_login = True unicode test: ok --Zhuyifei1999 (talk) 06:09, 1 June 2013 (UTC)
 * ok, thanks for that hint. Xqt (talk) 14:06, 1 June 2013 (UTC)
 * BTW, I moved my bot to labs, and updated, there's still the error.

zhuyifei1999@tools-login:~/pywikipedia$ python category_redirect.py No handlers could be found for logger "pywiki" WARNING: Your account on commons:commons does not have a bot flag. Its edits will be visible in the recent changes and it may get blocked. Getting 3 pages from commons:commons... WARNING: Missing namespace in family file commons: namespace['commons'][1198] (it is set to 'Translations') WARNING: Missing namespace in family file commons: namespace['commons'][1199] (it is set to 'Translations talk') Retrieving watchlist for commons:commons via API. Updating page via API Done checking hard-redirect category pages. Traceback (most recent call last): File "category_redirect.py", line 579, in    main File "category_redirect.py", line 574, in main bot.run File "category_redirect.py", line 409, in run prop='info|categoryinfo'): File "category_redirect.py", line 266, in query_results    querydata.update(result['query-continue'][query_type]) NameError: global name 'query_type' is not defined zhuyifei1999@tools-login:~/pywikipedia$ python version.py Pywikipedia [http] trunk/pywikipedia (r11602, 2013/06/01, 11:23:55, OUTDATED) Python 2.7.3 (default, Aug  1 2012, 05:14:39) [GCC 4.6.3] config-settings: use_api = True use_api_login = True unicode test: ok --Zhuyifei1999 (talk) 00:44, 2 June 2013 (UTC)
 * 10485reverted in 11610. Xqt (talk) 09:19, 2 June 2013 (UTC)
 * Thanks. --Zhuyifei1999 (talk) 09:53, 2 June 2013 (UTC)

Another bug
This keeps on coming out when I edit commons on too labs: zhuyifei1999@tools-login:~$ python ~/pywikipedia/touch.py -page:"Category talk:Icons for motorway descriptions/generic" No handlers could be found for logger "pywiki" Getting 1 page from commons:commons... NOTE: You have new messages on commons:commons WARNING: Your account on commons:commons does not have a bot flag. Its edits will be visible in the recent changes and it may get blocked. Sleeping for 4.8 seconds, 2013-06-16 10:03:01 Updating page Category talk:Icons for motorway descriptions/generic via API HTTPError: 504 Gateway Time-out WARNING: Could not open 'http://commons.wikimedia.org/w/api.php'. Maybe the server is down. Retrying in 1 minutes... zhuyifei1999@tools-login:~$ python ~/pywikipedia/version.py Pywikipedia [http] trunk/pywikipedia (r11641, 2013/06/11, 13:14:57, ok) Python 2.7.3 (default, Aug 1 2012, 05:14:39) [GCC 4.6.3] config-settings: use_api = True use_api_login = True unicode test: ok This time I don't know what's wrong. The server is not down since I can still access commons. --Zhuyifei1999 (talk) 04:17, 12 June 2013 (UTC)

Seems that when saving large pages, it always cause that error. --Zhuyifei1999 (talk) 02:19, 16 June 2013 (UTC)
 * Yes this might be. We have no abilities to fix it. Xqt (talk) 14:44, 19 June 2013 (UTC)

Warteschlange
Hallo xqt. Bei der Pywikipedia-Version, die ich 2012 oder 2013 auf meinem alten PC installiert hatte, gab es eine Warteschlange von 60(?) halbautomatischen Edits, die gefüllt werden konnte. Bei der gestern installierten Version (Core) scheint dies nicht der Fall zu sein, so dass ich schon noch wenigen Edits waren musste, bis diese ausgeführt wurden, um die nächste Änderungsvorschau angezeigt zu erhalten. Kann man dies irgendwo ändern? Im Manual habe ich nichts dazu gefunden. --Leyo 00:03, 9 January 2015 (UTC)
 * Hi Leyo, welches Script? solve-disambiguation.py? @ xqt 04:05, 9 January 2015 (UTC)
 * Ich hab' mir obiges Script mal angeschaut und nichts auffälliges gefunden. Es warden bis zu 64 Seiten gesammelt und asynchrony bearbeitet. Kanst Du mal in den Chat oder  kommen, damit wir das mal durchgehen. Vielleicht ist ja doch noch irgenwo der Wurm drin.  @ xqt 04:50, 9 January 2015 (UTC)
 * Nein, replace.py. Du scheinst gerade nicht im Chat zu sein. --Leyo 19:26, 9 January 2015 (UTC)
 * ja, seit halb acht war ich offline. Kannst ja per Gelegenheit nochmal probieren, bin eigentlich häufig anzutreffen. Aber egal: Ich schau mir morgen das Script mal an und geb' Dir Bescheid. Aus dem Stand weiß ich's nicht. @ xqt 20:52, 9 January 2015 (UTC)
 * Also ich habe das Script mal geprüft, demnach sollte es so funktionieren, wie Du es erwartest. Wir müssten das mal an einem Beispiel durchspielen. @ xqt 10:41, 10 January 2015 (UTC)

Login Pywikipedia
Hallo Xqt,

seit kurzem kann ich mich mit login.py nicht mehr einloggen. Wenn ich login.py unter chdir \pywikipedia (wo ich pywikipedia gespeichert habe) einfüge, kommt nicht einmal eine Fehlermeldung, sondern chdir \pywikipedia wird einfach wiederholt.

Was mache ich falsch?

Gruß, --Holder (talk) 14:17, 4 July 2015 (UTC)
 * Hallo, ich verstehe nicht genau, was Du meinst; Du fügst ein Script ein? Mit welcher Version arbeitest Du den, compat oder core? und was kommt heraus, wenn Du version.py ausführst? Kannst Du mal in den Chat kommen. Ich bin da oft. Ansonsten sind da jayvdb und xzise häufig, die gerne helfen. Gruß @ xqt 19:00, 4 July 2015 (UTC)
 * Chat, hm, muss mal schauen, ob ich dazu komme.
 * Wenn ich version.py eingeben kommt folgendes:

Pywikipedia [http] trunk/pywikipedia (r10875, 2013/01/05, 22:45:20) Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] config-settings: use_api = True use_api_login = True unicode test: ok
 * Vermutlich alles völlig veraltet, oder?
 * Gruß, --Holder (talk) 17:41, 5 July 2015 (UTC)
 * Ja sehr. Diese Version kann seit spätesten letzter Woche gar nicht mehr laufen weil sich die API geändert hat. Ich kann da nur raten, den Bot zu aktualisieren und am besten zu core-Version zu wechseln. Die alte compat-Version wird von den Entwicklern nicht mehr unterstützt, läuft aber noch. Grüße @ xqt 21:29, 5 July 2015 (UTC)
 * Danke, werde ich versuchen, aber vor den Sommerferien wird das nichts mehr. Melde mich evtl. danach wieder. Viele Grüße, --Holder (talk) 20:26, 7 July 2015 (UTC)

pywikibot/bots/xqbot tests
Hi !

I was looking at layout.yaml and saw - name: pywikibot/bots/xqbot template: - name: tox-jessie but I fail to understand where the tests it runs are actually defined. I guess it will run tox but ... how does it go from the stanza in layout.yaml to running the tox command ? I'm asking because I'd like to prepare tests for a bot I'm writing and would like to follow your example.

Thanks ! Dachary (talk) 08:22, 29 July 2016 (UTC)

welcome.py: problem for zh
Hi Xqt, I wanted to run this script on srwiki. When I wanted to run, I got:

Traceback (most recent call last): File "pwb.py", line 263, in    if not main: File "pwb.py", line 256, in main run_python_file(filename, [filename] + args, argvu, file_package) File "pwb.py", line 120, in run_python_file exec(compile(source, filename, "exec", dont_inherit=True), File ".\scripts\welcome.py", line 336    'zh': u'\n* ' + timeselected,       ^ SyntaxError: invalid syntax CRITICAL: Closing network session. 

I tryed with copying syntax for enwiki, but no effects. What to I work? I tryed too with -lang:sr but no effects. Zoranzoki21 (talk) 16:10, 13 October 2017 (UTC)
 * Pastebin Zoranzoki21 (talk) 16:13, 13 October 2017 (UTC)
 * Script worked normal before my patch, but I no touched parameters for zhwiki in patch. Zoranzoki21 (talk) 16:19, 13 October 2017 (UTC)
 * Probably you are using an older patchset e.g. this one. I cannot reproduce that failure and the syntax checking is ok:

>>> import pwb, pywikibot as py >>> from scripts import welcome >>>
 * You should update your bot. @ xqt 12:56, 14 October 2017 (UTC)
 * Thank you! I downloaded pywikbot from gerrit with git clone and it resolved a problem. Thank you! Zoranzoki21 (talk) 13:28, 14 October 2017 (UTC)

Please review with +2 patch again
HI, can you again add +2 on patch https://gerrit.wikimedia.org/r/#/c/383932/? I removed your vote because change is not deployed. You can see in comment. Zoranzoki21 (talk) 13:04, 15 October 2017 (UTC)
 * Done. @ xqt 16:48, 15 October 2017 (UTC)
 * Thank you! Zoranzoki21 (talk) 16:51, 15 October 2017 (UTC)

Non-JSON response
Hi Xqt. Your observation about the put_throttle is right (infact I asked how it could solve the problem), but the script always locks up after 10-15 minutes of work. I have limited experience as a programmer, but that thing sounds like a bug. Any other script runned on bot with more substation works normally. Something is not working well. Bye, -- .av gas  07:48, 18 February 2018 (UTC)
 * I've runned that script in -simulate mode for more than 1 hour without any problems. Looks like an connection problem on your side. The fact is that the received data from server is malformed. For futher exploring the complete log would be helpful. Also run that script in -verbose mode to get additional outputs. The logfile will increase a lot. @ xqt 09:16, 18 February 2018 (UTC)
 * I runned that script for six hours without any problems. @ xqt 13:53, 18 February 2018 (UTC)

Inactive bot account
Hi. At Project:Requests/User rights/Removal of inactive bot rights (2) there is a proposal to remove the bot rights of inactive bots. Since you appear to be the operator of one of the bots in question, I wanted to draw your attention to the discussion. Please let us know if the rights are still needed (or if they aren't). Thanks, --DannyS712 (talk) 02:47, 29 July 2020 (UTC)
 * I think I don't need them currently. @ xqt 11:26, 3 October 2020 (UTC)
 * In that case, would you like me to remove the bot flag from User:Xqbot? DannyS712 (talk) 20:40, 3 October 2020 (UTC)

Help
Hey there, Xqt! :)

I wanted to ask you 2 things. First of all, has the change about summary been deployed yet? I got a lot of emails from the tests but wasn't able to follow them all and I thought I'd take the shortcut by asking here.

Secondly, can you help me with a weird problem I've been having while accessing the REST API with my bot? (Not related to pywikibot per se.) I've created a while loop to send some POST and GET requests in a row with curl in a certain wiki page. The bizarre part is that I get this pattern: 2 iterations of the loop go well and in the 3rd one I get an edit conflict, even though no one is editing that page other than me (other than my bot, better said). And this repeats until the end of the loop. In the end, 1/3 of the total requests hasn't gone through because of having faced "edit conflicts" (HTTP CODE 409). I believe it is related to the id revision parameter. It somehow gets confused and tries to edit an old version and that brings the edit conflict but I can't solve it even if I make the requests go through very slow (1 every 10 minutes, for example), the pattern is always there. The only way for the pattern to change is to make it send the requests without any kind of sleep in between, in which case more than 3/4 of the requests start facing edit conflicts, so it gets worse, 1/3 is the best I can do. Do you have any idea what might be happening given your technical knowledge? What might be sending HTTP 409 codes when in reality there is not really an edit conflict happening? I can provide more information if needed. - Klein Muçi (talk) 11:20, 8 March 2021 (UTC)
 * During these days, I've tried the summary change many times but nothing happens. Maybe I'm applying it wrong? What I do is, at my user-fixes.py, put this: 'msg': {'_default':'Example text: Lorem ipsum bla bla bla%(description)s',} but I only get the literal string as written for a summary. What am I doing wrong? - Klein Muçi (talk) 02:07, 15 March 2021 (UTC)
 * Sorry for this late response. The change for the summary message was deployed with release 6.0.0 for weeks ago. Please verify your Pywikibot version.
 * The second point: HTTP CODE 409 is not an edit conflict but a request conflict:


 * This indicates a conflict with the current state of the target resource but I cannot say what this really means. Because this is a server response I guess this has nothing to do with pywikibot. Probably adding a get throttle or increasing put_throttle would help. Look at config2.py for those settings.
 * Best @ xqt 09:04, 13 April 2021 (UTC)
 * Thanks for the answer! :)) I think you mean user-config.py, no? There put_throttle is equal to 10. Should I increase it more? I thought the default (10 seconds) was good enough. - Klein Muçi (talk) 11:38, 13 April 2021 (UTC)
 * The documentation for the settings are in . The idea for increasing the put throttle is that the server (target resouce) needs some additional time. But this is not sure bu you can try it whether it helps. You may just add an additional option to your command line e.g.   and increase the put throttle to 30 seconds. You also may use   fro example which slows down read requests from server to 5 seconds. Play with these parameter, probably it helps. Otherwise you have to contact the target resource provider about that http status. Best  @ xqt 12:10, 13 April 2021 (UTC)
 * Okay then. I'll try playing around with those. Thank you! As for contacting the target resource provider... My bot is active on the Albanian Wikipedia and Wikiquote (I'm an admin on those sites). Do you have any idea where who can I contact in these cases? I may need some guidance in regard to accessing the Wikipedia's API in general anyway so... Just for future reference. - Klein Muçi (talk) 12:48, 13 April 2021 (UTC)
 * I've not glue. Probably wikitech. I am not familar with REST API and Pywikibot does only support the http interface yet (maybe you can contribute some code ;) @ xqt 13:17, 13 April 2021 (UTC)

Hey there! I played around with those values and even the API retry number values. It doesn't seem to make any difference. The pattern is always there and always the same: 2 requests go through, 1 doesn't. I get this message:  {"messageTranslations":{"sq":"Konflikt në redaktim.","en":"Edit conflict."},"httpCode":409,"httpReason":"Conflict"}  Does it tell you anything? - Klein Muçi (talk) 09:26, 14 April 2021 (UTC)
 * Today I had some free time and I looked at the verbose mode out of curiosity to compare the requests when they got through and when they didn't.
 * This is when the request goes through and this is when it doesn't. The cache part looks the most interesting part even though I don't know what it means. (Also some minor changes like cookies, etc.) Please take a look at them whenever you have some free time. Maybe you understand more than I do.
 * As always the pattern is always 2 go, 1 doesn't.
 * Also, please take a look here. According to the instructions on that page, error 409 is sent on edit conflict cases. There are no edits happening in that page apart from those that my bot is doing so that leaves the problem to be related with the revision ID. In the way I've set up the script, the latest revision ID is taken automatically by a variable but still gives problems 1/3 of the time. Maybe it's a problem related to caching somehow? - Klein Muçi (talk) 09:06, 24 April 2021 (UTC)
 * As always the pattern is always 2 go, 1 doesn't.
 * Also, please take a look here. According to the instructions on that page, error 409 is sent on edit conflict cases. There are no edits happening in that page apart from those that my bot is doing so that leaves the problem to be related with the revision ID. In the way I've set up the script, the latest revision ID is taken automatically by a variable but still gives problems 1/3 of the time. Maybe it's a problem related to caching somehow? - Klein Muçi (talk) 09:06, 24 April 2021 (UTC)
 * Also, please take a look here. According to the instructions on that page, error 409 is sent on edit conflict cases. There are no edits happening in that page apart from those that my bot is doing so that leaves the problem to be related with the revision ID. In the way I've set up the script, the latest revision ID is taken automatically by a variable but still gives problems 1/3 of the time. Maybe it's a problem related to caching somehow? - Klein Muçi (talk) 09:06, 24 April 2021 (UTC)

Gerrit
Hi, Xqt. Hope that you are well. Could you, please, resolve the issue of 676780? The commit has been open for 3 days now without comment from your side. Wishing you the best in your life. Cheers. --Meno25 (talk) 16:55, 9 April 2021 (UTC)


 * Thank you ❤️ If we were living in the same city, I would have bought you a beer. Much appreciated. Cheers. --Meno25 (talk) 19:17, 10 April 2021 (UTC)
 * Thanks. I'll drink a beer to you and appreciate your contribs. @ xqt 08:45, 12 April 2021 (UTC)

T267742
Hi, Xqt. Hope that you are doing well. I don't want to take much of your time but I would like to draw your attention to this comment. My understanding is that this bug can be resolved quickly, so, can you resolve it for me? Thank you and best wishes for you always. --Meno25 (talk) 15:24, 18 May 2021 (UTC)
 * Hi Meno25, I am sorry I tried to find a more general solution for such an exception. Now I've implemented one for this script only. The problem is the lazy parsing of title but any earlier status has deeper impacts. Unfortunately I found a big problem with the implementiation of output cache from compat. It always fails on tests if the testing CPU is highly used T282962 but I haven't found problems for a normal run. Please have a look on it if something looks courious with pywikibot.output and other logger. I think I'll revert it for 6.2 and postpone that to 6.3. Thanks a lot. @ xqt 20:12, 18 May 2021 (UTC)

Pywikibot, Script "category" und Anführungszeichen
Tach, Xqt, nachdem letztens das Problem bei mir lag, frage ich jetzt lieber erstmal: Kann es sein, dass das Skript „category“ nicht mit Anführungszeichen umgehen kann? Mir fiel das im Barwiki auf, aber nicht nur dort gibt es Kategorien mit Doppelpunkten im Namen.
 * führte nicht unerwartet zur Fehlermeldung


 * führte ebenso erwartet zur selben Fehlermeldung. In der commands.log sind die Befehlsaufrufe auch identisch.

Nun aber zu den unerwarteten Ergebnissen:
 * ergibt


 * führt zu

Die Kat. ist sehr wohl existent: bar:Kategorie:Spruch:Person.

Eine Anführung um den Parameter wie im zweiten Beispiel, um Leerzeichen in Kategorien abzufangen, stellt dagegen kein Problem dar. — Speravir (talk) – 23:08, 10 June 2021 (UTC)
 * zu : Spruch:Person ist aber keine Kategorie oder wird nicht als solche erkannt wegen des Namensraum-Präfixes.   sollte dagegen funktionieren.  @ xqt 11:37, 16 June 2021 (UTC)