You should not be collecting user passwords since doing so would compromise the account. Use OAuth instead.
Where is CheckUser not deployed?
Beta Cluster, which shouldn't have it.
Mon, Nov 28
Thu, Nov 24
You must run the command as the tool, not your user.
Wed, Nov 23
See T223002#5843155 for a previous issue with using mw.user.options.get('timecorrection') prior to refactoring (rMW65c955746c59: Split TimeCorrection parser into separate class). For ZoneInfo, the offset in the database is unreliable and the timezone name needs to be used. Just get rid of it (T322352).
Mon, Nov 21
Sun, Nov 20
Fri, Nov 18
Wed, Nov 16
Prevents account creation: ipb_create_account = 1
Email disabled: ipb_block_email = 1
Auto block enabled: ipb_enable_autoblock = 1
Sun, Nov 13
Sat, Nov 12
Each command has additional help text.
Fri, Nov 11
Thu, Nov 10
Wed, Nov 9
Mon, Nov 7
@eranroz It is prompting for your bot's password.
Sat, Nov 5
This is due to T314639 not being completed yet.
Fri, Nov 4
- My first issue was with the location of the pwb.py wrapper. Following step 5 doesn't work, even when using release 7.0.0 scripts location. What worked for me was calling python3 /data/project/shared/pywikibot/core/pwb.py generate_user_files. Since the files' location has changed and that's where new users will find them, should there still be a caution alert or should step 5 be updated with the new path and recommend calling pwb.py with arguments rather than the utility scripts directly?
The doc now uses pwb.
Thu, Nov 3
Tue, Nov 1
I can confirm it changed, but I don't know if it was intentional.
Oct 31 2022
Oct 30 2022
Oct 24 2022
Sure but is that really what is wanted?
Oct 23 2022
Thanks for the info. Is there a way to get Grafana to show CPU usage per pod, so I could see how often a pod is reaching the limits?
Oct 22 2022
Oct 20 2022
@DannyS712: Since you worked on the related tasks, any chance you would be interested in implementing this?
Oct 19 2022
You only need one setup.py that will install multiple site-packages. I did some quick testing by updating as below and things seem to work. It installs 3 site-packages: pywikibot, pywikibot_i18n, and pywikibot_scripts.
Oct 18 2022
If you don't want to put it run.sh, I think --command "cd foo && PAGES_ARTICLES=/public/dumps/public/enwiktionary/20220720/*pages-articles.xml.bz2 MODULE_DB=modules.sqlite TRANSLATION_DB=translations.sqlite ./run.sh" should work.
Oct 17 2022
there are some modules missing in the "shared Pywikibot files (recommended setup)"
We shouldn't be using a custom way to make the distribution. That is just asking for things to be broken like this.
Oct 15 2022
Oct 14 2022
https://k8s-status.toolforge.org/namespaces/tool-anomiebot/ has quota information and a link to Grafana.
Oct 12 2022
Oct 11 2022
Based on the path, it is the entry point (not exe since it is linux).
The warning also looks incorrect.
Oct 10 2022
Oct 9 2022
Oct 7 2022
None of the emails are working per a report on IRC.
Oct 6 2022
Oct 4 2022
This solves the issue you are concerned with no?
I think there should be no problem having no retries at all and let the user re-run the job if required.
Oct 1 2022
All bot jobs (eswiki, enwiki, and frwiki) stopped until the account issue is resolved.
There were some edits that were uploaded and checked after that one, but it effectively stopped not long after that - the scheduled restart that just after midnight.