[09:22:18] Toolforge jobs not firing? [09:33:05] Yetkin: do you have more details? [10:00:30] Hmm, has there been a change affecting the login system? My bot can longer log into the api [11:07:59] @Yetkin, what is your bot? [12:04:25] !log lucaswerkmeister@tools-bastion-13 tools.ranker deployed 32a85a522b (l10n updates: nl) [12:04:27] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.ranker/SAL [12:16:57] !log lucaswerkmeister@tools-bastion-13 tools.speedpatrolling deployed c24b959679 (style fixes) [12:16:59] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.speedpatrolling/SAL [14:50:16] It is YBot (re @wmtelegram_bot: @Yetkin, what is your bot?) [15:23:45] The result of the API call is as follows. [15:23:45] [error] => Array [15:23:46] ( [15:23:48] [code] => readonly [15:23:49] [info] => The database has been automatically locked while the replica database servers catch up to the primary [15:23:51] [readonlyreason] => Waiting for 6 lagged database(s) [15:23:52] [*] => See https://tr.wikipedia.org/w/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes. [15:23:54] ) [15:23:55] [servedby] => mw-api-ext.eqiad.main-77fc5fd75f-nt4rf [15:24:36] I cannot see any replag for s2 (trwiki) by the way [15:30:54] @Yetkin I can see there was some replag for s2 a few minutes ago, but now looks fine [15:31:52] Now [15:31:54] [login] => Array [15:31:55] ( [15:31:57] [result] => Failed [15:31:58] [reason] => The supplied credentials could not be authenticated. [15:32:00] ) [15:34:29] This bot worked fine until yesterday. What has changed? [15:38:00] Can you log in via a browser using the bots credentials? [15:42:23] Reedy: yes, I can [15:43:40] When did it last try and API login? [15:44:51] 13 minutes ago [15:45:14] The response was [15:45:15] [login] => Array [15:45:16] ( [15:45:18] [result] => Failed [15:45:19] [reason] => The supplied credentials could not be authenticated. [15:45:21] ) [15:53:08] I see a login that apparently worked a couple of mins ago from a cloud IP [15:53:10] 2025-04-01 15:49:07.690585 [c6e33e62-b02e-4b2b-aa0c-610d8a0adcbf] mw-api-ext.eqiad.main-77fc5fd75f-rg6k6 trwiki 1.44.0-wmf.22 authentication INFO: Login for YBot succeeded from 172.16.2.217 {"user":"YBot","clientip":"172.16.2.217"} [15:56:40] Reedy: this is weird... It worked once a few minutes ago but when I try my toher scripts, they fail with the same error message. Can you see my failed login attempts? [15:58:31] Nope... I'm not seeing any evidence of failed attempts [15:58:46] which is odd in itself [16:03:40] Reedy: oh my, this is really weird... [16:03:40] I tried to empty my cookie jar and it worked. The downside is that I have to empty that file aftereach API request, which is really bad. [16:03:42] This used to work fine earlier. What can be the probelm? [16:04:03] Some SUL3 related changes? [16:05:18] how? [16:11:21] anyone with the same problem? this is really annoying [16:21:24] [step-analyze] 2025-04-01T16:16:18.214105896Z Image with name "tools-harbor.wmcloud.org/tool-campwiz-bot/tool-campwiz-bot:latest" not found [16:21:25] [step-detect] 2025-04-01T16:16:18.799905705Z 1 of 4 buildpacks participating [16:21:27] [step-detect] 2025-04-01T16:16:18.799949413Z heroku/go 0.1.13 [16:21:28] [step-restore] 2025-04-01T16:16:03.152587322Z 2025/04/01 16:16:03 warning: unsuccessful cred copy: ".docker" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.docker/config.json: permission denied [16:21:30] [step-build] 2025-04-01T16:16:19.525997767Z [16:21:31] [step-build] 2025-04-01T16:16:19.526040667Z [Reading build configuration] [16:21:33] [step-build] 2025-04-01T16:16:19.531682222Z Detected Go version requirement: =1.24.1 [16:21:34] [step-build] 2025-04-01T16:16:19.532169801Z [16:21:36] [step-build] 2025-04-01T16:16:19.532178566Z [Error: Heroku Go Buildpack version resolution error] [16:21:37] [step-build] 2025-04-01T16:16:19.532184164Z Couldn't resolve go version for: =1.24.1 [16:21:39] [step-build] 2025-04-01T16:16:19.533192370Z ERROR: failed to build: exit status 1 [16:21:40] [step-fix-nested-procfile-launcher] 2025-04-01T16:16:19.782115599Z 2025/04/01 16:16:19 Skipping step because a previous step failed [16:21:42] [step-fix-imagemagick-config] 2025-04-01T16:16:20.220495791Z 2025/04/01 16:16:20 Skipping step because a previous step failed [16:21:43] [step-fix-permissions] 2025-04-01T16:16:20.510363510Z 2025/04/01 16:16:20 Skipping step because a previous step failed [16:21:45] [step-export] 2025-04-01T16:16:06.206859325Z 2025/04/01 16:16:06 warning: unsuccessful cred copy: ".docker" from "/tekton/creds" to "/tekton/home": unable to open destination: open /tekton/home/.docker/config.json: permission denied [16:21:46] [step-export] 2025-04-01T16:16:21.244332203Z 2025/04/01 16:16:21 Skipping step because a previous step failed [16:21:48] [step-results] 2025-04-01T16:16:21.431211714Z 2025/04/01 16:16:21 Skipping step because a previous step failed [16:21:49] (venv) tools.campwiz-bot@tools-bastion-13:~$ [16:22:22] I am getting this issue while building an image for golang 1.24.1 [16:51:19] Reedy: enabled BotPasswords and after using it once, I am getting this error [16:51:19] [login] => Array [16:51:21] ( [16:51:22] [result] => Aborted [16:51:24] [reason] => Cannot log in when using MediaWiki\Session\BotPasswordSessionProvider sessions. [16:51:25] ) [16:53:16] tgr_: ^^ [16:53:31] if you’re using a bot password, make sure you use `action=login` and not `action=clientlogin` – I think that error message might mean `clientlogin` [16:53:36] (apologies if that’s not the problem after all) [16:55:51] using action=login [16:57:10] ok [16:57:52] (FWIW I just tried running the https://github.com/lucaswerkmeister/m3api-botpassword/ integration tests a couple of times and they all passed, so I’m not seeing any bot password issues on my end…) [17:02:11] are you logging out at the end of execution? [17:04:18] yes [17:08:21] what if you try to run a script when you are already logged in= This is the exact scenario I am workişng on right now [17:08:59] I have multiple scripts running at the same time and each one of them is trying to log in at first [17:13:48] still works AFAICT [17:14:00] does not work for me [17:14:24] another question: When does the session time out when using BotPasswords? [17:19:29] no idea… my expectation would be that they’re valid for a long time, on the order of months at least [17:19:38] I skimmed the code a bit and didn’t see any obvious hard time limit [17:40:57] do botpasswords impersonate my bot acount? I need something like this [18:11:06] if you create a botpassword from your bot account, then yes. (re @Yetkin: do botpasswords impersonate my bot acount? I need something like this) [18:55:29] !log wikistats deployed new update-miraheze code and started script [18:55:31] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikistats/SAL [19:05:15] !log wikistats purge http!=200 from Miraheze table [19:05:17] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikistats/SAL