Page MenuHomePhabricator

MBH (Max)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Saturday

  • Clear sailing ahead.

User Details

User Since
Oct 7 2014, 11:57 AM (510 w, 1 d)
Availability
Available
LDAP User
Maxbiohazard
MediaWiki User
MBH [ Global Accounts ]

Recent Activity

Tue, Jul 9

MBH added a comment to T365476: Wikimedia maps, scaled several times, can't be closed.

Now it happens on https://ru.wikipedia.org/wiki/%D0%9A%D0%B0%D0%BD%D1%82%D0%B0%D1%82%D1%81%D0%BA%D0%BE%D0%B5_%D0%B2%D0%BE%D0%B4%D0%BE%D1%85%D1%80%D0%B0%D0%BD%D0%B8%D0%BB%D0%B8%D1%89%D0%B5

Tue, Jul 9, 10:43 AM · Maps (Kartographer)

Fri, Jul 5

MBH added a comment to T365476: Wikimedia maps, scaled several times, can't be closed.

Now it happens on https://ru.wikipedia.org/wiki/%D0%96%D0%B8%D0%BB%D0%BE%D0%B9_%D0%BA%D0%BE%D0%BC%D0%BF%D0%BB%D0%B5%D0%BA%D1%81_%D0%B4%D0%BB%D1%8F_%D1%81%D0%BB%D1%83%D0%B6%D0%B0%D1%89%D0%B8%D1%85_%D0%A4%D0%B8%D0%BD%D0%BB%D1%8F%D0%BD%D0%B4%D1%81%D0%BA%D0%BE%D0%B9_%D0%B6%D0%B5%D0%BB%D0%B5%D0%B7%D0%BD%D0%BE%D0%B9_%D0%B4%D0%BE%D1%80%D0%BE%D0%B3%D0%B8
See the screenshot - a string "#/maplink/0" in the end of the URL was removed, but map still overlaps the article.

image.png (1×2 px, 1 MB)

Fri, Jul 5, 11:14 AM · Maps (Kartographer)

Sun, Jun 30

MBH added a comment to T368380: FlaggedRevs: moved page gets unreviewed.

Try to rename any page on a live ruwiki (see merged task).

Sun, Jun 30, 3:43 PM · MW-1.43-notes (1.43.0-wmf.13; 2024-07-09), Regression, MediaWiki-extensions-FlaggedRevs
MBH created T368842: Page moves now unreviews pages (Flagged Revs).
Sun, Jun 30, 6:35 AM · MediaWiki-Page-rename, MediaWiki-extensions-FlaggedRevs

Jun 17 2024

MBH changed the status of T365476: Wikimedia maps, scaled several times, can't be closed from Stalled to Open.

Now it happen on https://ru.wikipedia.org/wiki/%D0%9D%D0%BE%D0%B2%D0%BE-%D0%90%D0%B4%D0%BC%D0%B8%D1%80%D0%B0%D0%BB%D1%82%D0%B5%D0%B9%D1%81%D0%BA%D0%B8%D0%B9_%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB . Console:

Jun 17 2024, 1:58 AM · Maps (Kartographer)

Jun 15 2024

MBH created T367626: Time period cannot be selected on pageviews.wmcloud.org on mobile.
Jun 15 2024, 6:51 AM · Tool-Pageviews, PageViewInfo

Jun 3 2024

MBH added a comment to T366456: How to read big set of pages without getting 429?.

@Aklapper Could you tell me the name of any developer who you think could help me with this?

Jun 3 2024, 9:36 AM · MediaWiki-libs-HTTP
MBH created T366456: How to read big set of pages without getting 429?.
Jun 3 2024, 9:32 AM · MediaWiki-libs-HTTP

May 30 2024

MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

You mostly fixed these bots in March, but two bots, sandbox and autopurge (and three tasks, because second bot is runned as two tasks, autopurge-daily and autopurge-hourly) fails every day because of some errors. When I tried to find a reason, I got tons of flood in .err files (we discuss this above), but looks like I found an actual reason of this crashes.

May 30 2024, 1:36 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

You can replace the logging.info with bare print statements, that will not add the timestamps, but will make them go to stdout (simplest).

There are many strings like this in .err file and looks like there are no such strings in the bot code:

Sleeping for 8.9 seconds, 2024-05-30 11:00:20
Sleeping for 9.7 seconds, 2024-05-30 11:00:29
Sleeping for 9.7 seconds, 2024-05-30 11:00:39
Sleeping for 9.6 seconds, 2024-05-30 11:00:49
Sleeping for 9.7 seconds, 2024-05-30 11:00:59
Sleeping for 8.8 seconds, 2024-05-30 11:01:10

or

Sleeping for 8.8 seconds, 2024-05-29 14:10:15
Page [[Википедия:Песочница]] saved
Sleeping for 9.3 seconds, 2024-05-29 14:10:25
Page [[Обсуждение Википедии:Песочница]] saved
Sleeping for 9.6 seconds, 2024-05-29 14:10:35
Page [[Инкубатор:Песочница]] saved
Sleeping for 9.3 seconds, 2024-05-29 14:10:45
Page [[Шаблон:Песочница]] saved
Sleeping for 9.4 seconds, 2024-05-29 14:10:55
Page [[Шаблон:Песочница/doc]] saved

Looks like this strings are generated by pywikibot framework itself and I think they posting can be avoided only by refusal to use pywikibot.

May 30 2024, 1:11 PM · Grid-Engine-to-K8s-Migration

May 29 2024

MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

This script is runned from this fragment of jobs.yaml:

- name: sandbox
  command: sandbox
  image: tool-wikisaurusbot/tool-wikisaurusbot:latest
  schedule: "*/5  * * * *"
  emails: onfailure
  mount: all
  filelog: true
May 29 2024, 10:26 AM · Grid-Engine-to-K8s-Migration

May 28 2024

MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

@dcaro A script sandbox.py generates an error Skipped '/workspace/user-config.py': owned by someone else. I don't see workspace folder on Toolforge filesystem, looks like this is a folder in built image, how to solve this problem in this case?

May 28 2024, 6:31 PM · Grid-Engine-to-K8s-Migration

May 24 2024

MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

This bots has also a strange issue: they write messages about correct working into error stream, see contents of files techtasks.err, autopurge-daily.err for example. This messages should be redirected to .out stream, and .err files should contain only messages about crashes.

@dcaro could you fix this? What do I need to do, for example in file https://github.com/wikisaurus/wikisaurusbot/blob/master/facenapalmscripts/autopurge.py : delete a logging section?

May 24 2024, 11:19 AM · Grid-Engine-to-K8s-Migration

May 23 2024

MBH closed T360839: I can't connect to Toolforge DB replicas from my PC using MySQL Workbench as Resolved.

After explicitly indicating ports (4711 and 4712) in connection strings (before that, port wasn't defined in CS) all works, both connections in one time.

May 23 2024, 1:32 PM · Toolforge (Toolforge iteration 10)
MBH added a comment to T360839: I can't connect to Toolforge DB replicas from my PC using MySQL Workbench.

After re-converting .ppk key, I successfully logged into Toolforge in Powershell window:

PS C:\Windows\system32> ssh -L 4711:ruwiki.web.db.svc.wikimedia.cloud:3306 mbh@login.toolforge.org
The authenticity of host 'login.toolforge.org (...)' can't be established.
ECDSA key fingerprint is SHA256:...
Are you sure you want to continue connecting (yes/no/[fingerprint])? y
Please type 'yes', 'no' or the fingerprint: yes
Warning: Permanently added 'login.toolforge.org,...' (ECDSA) to the list of known hosts.
Linux tools-bastion-13 6.1.0-17-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.69-1 (2023-12-30) x86_64
Debian GNU/Linux 12 (bookworm)
tools-bastion-13 is a Toolforge bastion (wmcs::toolforge::bastion)
<...>
mbh@tools-bastion-13:~$

I opened ukwiki's DB in the second PS window. But after that, my bot still can't connect to DB with the same error:
MySql.Data.MySqlClient.MySqlException: "Unable to connect to any of the specified MySQL hosts."
even after replacement server address to 127.0.0.1 (and without this replacement) in connection string.

May 23 2024, 1:04 PM · Toolforge (Toolforge iteration 10)
MBH added a comment to T360839: I can't connect to Toolforge DB replicas from my PC using MySQL Workbench.

You are using the default port there, that's the issue, so you have two options:

  • Configure a different port in your code (maybe by reading an environment variable, or similar)
  • Open the tunnel on your local port 3306, instead of 4711

Sadly, I don't even know how to do both options. I have never did this, I just do

connect = new MySqlConnection(creds[2].Replace("%project%", "ruwiki").Replace("analytics", "web"));
connect.Open();
sqlreader = new MySqlCommand(commandtext, connect).ExecuteReader();
sqlreader.Read()...
May 23 2024, 12:21 PM · Toolforge (Toolforge iteration 10)
MBH updated subscribers of T360839: I can't connect to Toolforge DB replicas from my PC using MySQL Workbench.

@dcaro I tried to use another connection method, provided by @Iluvatar , looking simpler. It uses MS PowerShell:

PS C:\Windows\system32> Get-Service ssh-agent | Set-Service -StartupType Automatic
PS C:\Windows\system32> Start-Service ssh-agent
PS C:\Windows\system32> ssh-add C:\Users\max\ssh.ppk
Enter passphrase for C:\Users\max\ssh.ppk:
Identity added: C:\Users\max\ssh.ppk (C:\Users\max\ssh.ppk)

But on last step I got this error:

PS C:\Windows\system32> ssh -L 4711:ruwiki.web.db.svc.wikimedia.cloud:3306 mbh@login.toolforge.org
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The ED25519 host key for login.toolforge.org has changed,
and the key for the corresponding IP address ....
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ED25519 key sent by the remote host is
SHA256:....
Please contact your system administrator.
Add correct host key in C:\\Users\\max/.ssh/known_hosts to get rid of this message.
Offending ED25519 key in C:\\Users\\max/.ssh/known_hosts:1
ED25519 host key for login.toolforge.org has changed and you have requested strict checking.
Host key verification failed.

I got errors looking like this every time I establish connection to Toolforge first time (after OS reinstall or from another device), and I ignore warnings looking like this, but when I tried to run my bot from my PC, the error still here:
MySql.Data.MySqlClient.MySqlException: "Unable to connect to any of the specified MySQL hosts."

May 23 2024, 12:11 PM · Toolforge (Toolforge iteration 10)

May 21 2024

MBH created T365477: Queued Quarry queries can't be stopped.
May 21 2024, 1:42 PM · Quarry
MBH created T365476: Wikimedia maps, scaled several times, can't be closed.
May 21 2024, 1:36 PM · Maps (Kartographer)

Apr 24 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Thank you, but I prefer traditional "build locally - transfer to server - run exe file" way as way more convenient and simple. Another reason is that I really don't like to push any minor changes to repository, even testing and intentionally broking, it creates very dirty repository. I prefer to push to repo stable, tested, working code, but using your way I am forced to push to repo even testing code, written for debugging, program should break with this code. Maybe it's needed to create two repos for every program: one "dirty" and one with with meaningful tested changes. As old way works with traditional bots, unlike web services, I'm don't planning to switch to your way.

Apr 24 2024, 6:49 AM · Grid-Engine-to-K8s-Migration

Apr 23 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

How to specify, should run be one-time, regular or bot should be online permanently?

Apr 23 2024, 11:15 AM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Bot example: https://github.com/Saisengen/wikibots/blob/main/other-bots/checking-new-edits.cs
It creates one exe file.

Apr 23 2024, 11:13 AM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

I have. But how to run such bots in buildpacks? Now I use jobs.yaml and specify path to exe file, how to do it with buildpacks?

Apr 23 2024, 9:51 AM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

@dcaro A Visual Studio currently provides two types of console C# apps: old way, working on Windows only (or under mono), and a new "dotnet" way, claimed to be working on Linux natively. All of my bots are written on old way and runs under mono. I tried to rewrite one of my (non-web) bots on new way; there are also Discord wiki bot, written by one ruwiki user, and it is written on new way too. But I can't run both apps on k8s on Toolforge even on tf-mono68 image. It's sayed than such programs should be runned by command dotnet run appname.exe, but Toolforge says Unknown command: dotnet. They also can't be runned through mono because This is not a valid CLI image. There is Phab task in which a dotnet was installed to Toolforge for Hawkeye7 user, the task is completed, but where is dotnet?

Apr 23 2024, 5:26 AM · Grid-Engine-to-K8s-Migration

Apr 19 2024

MBH added a comment to T362952: An edit can't be rolled back if it's opened in desktop mode, but the entire wiki switched to mobile mode.

On diff view, I has provided the link.

Apr 19 2024, 12:22 PM · MediaWiki-Platform-Team (Radar), MediaWiki-Core-AuthManager, MobileFrontend
MBH created T362952: An edit can't be rolled back if it's opened in desktop mode, but the entire wiki switched to mobile mode.
Apr 19 2024, 7:01 AM · MediaWiki-Platform-Team (Radar), MediaWiki-Core-AuthManager, MobileFrontend

Apr 16 2024

MBH added a comment to T360839: I can't connect to Toolforge DB replicas from my PC using MySQL Workbench.

I don't and I won't be able to try until May 6, I'm not at home.

Apr 16 2024, 10:14 AM · Toolforge (Toolforge iteration 10)

Apr 15 2024

MBH added a comment to T362503: ORES doesn't work (at least for ru- and ukwiki).

Looks like ukwiki works now.

Apr 15 2024, 8:47 AM · Patch-For-Review, Machine-Learning-Team, ORES
MBH renamed T362503: ORES doesn't work (at least for ru- and ukwiki) from ORES doesn't work (at least for ruwiki) to ORES doesn't work (at least for ru- and ukwiki).
Apr 15 2024, 4:52 AM · Patch-For-Review, Machine-Learning-Team, ORES
MBH created T362503: ORES doesn't work (at least for ru- and ukwiki).
Apr 15 2024, 4:48 AM · Patch-For-Review, Machine-Learning-Team, ORES

Mar 27 2024

MBH added a comment to T360839: I can't connect to Toolforge DB replicas from my PC using MySQL Workbench.

The error looks like the same: The connection has not been established because the destination computer rejected the connection request 127.0.0.1:3306
I'm not configuring port in my code/client and does't even know how to do it, I use the same connection string that on Toolforge: Server=%project%.web.db.svc.wikimedia.cloud;Database=%project%_p;Uid=s52321;Pwd=///;CharacterSet=utf8mb4;SslMode=none;

Mar 27 2024, 1:53 PM · Toolforge (Toolforge iteration 10)
MBH added a comment to T360839: I can't connect to Toolforge DB replicas from my PC using MySQL Workbench.

Okay, I probably forgot that it's needed to set up the tunnel in PuTTY settings, and it seemed to me that MySQL Workbench creates tunnel for my app. But I set up tunnel in PuTTY according to manual:

image.png (442×452 px, 27 KB)

loaded key file, opened connection, entered name and password, successfully entered to Toolforge - but bot still can't connect to DB.

Mar 27 2024, 1:38 PM · Toolforge (Toolforge iteration 10)

Mar 25 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

@dcaro I can open https://mbh.toolforge.org/clusters.html , but not https://mbh.toolforge.org/elections.txt (404), but both files is in the new static files folder, what's the reason? It's due to file extension?

image.png (724×1 px, 172 KB)

Mar 25 2024, 3:40 PM · Grid-Engine-to-K8s-Migration

Mar 23 2024

MBH created T360839: I can't connect to Toolforge DB replicas from my PC using MySQL Workbench.
Mar 23 2024, 5:18 AM · Toolforge (Toolforge iteration 10)

Mar 20 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Thanks, works now.

Mar 20 2024, 2:56 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T359529: Future of flaggedtemplates feature.

In commit description you provide another info: stable (=last reviewed, not last) template versions still will be used in stabilized articles, and before that stabilized articles used not last reviewed versions of templates, but versions of templates, that was used on page in time of last reviewing of this page. If it is true, I support this decision even more, I didn't know about this overcomplicated mechanism.

Mar 20 2024, 12:18 PM · MW-1.43-notes (1.43.0-wmf.8; 2024-06-04), DBA, MediaWiki-extensions-FlaggedRevs

Mar 19 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Thank you very much, I will try to rewrite my tools to dotnet app in the coming weeks. But after you updated web server config, people complaining that https://mbh.toolforge.org/cgi-bin/cpf doesn't work. This page doesn't open, browser endlessly loads it, but access event has written into access.log with 200 code. Could you see?

Mar 19 2024, 12:31 AM · Grid-Engine-to-K8s-Migration

Mar 18 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

No, by default it doesn't output anything after I avoided using DotNetWikiBot framework. New version can be stable and not producing errors.

Mar 18 2024, 5:03 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

I stopped a bot to load a new version of it, now I re-runned it.

Mar 18 2024, 4:38 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

I will try this, but .err file is empty after many hours after crashes, it doesn't look like buffering/caching problem.

Mar 18 2024, 3:43 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

I also have a question. As far as I understand, an image we built, running my tools on k8s now, contains some virtual filesystem, and I can't view it like I viewed my public_html folder on Toolforge earlier. Could I view contents of this virtual filesystem in k8s image some way?

Mar 18 2024, 3:08 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319676: Migrate dibot from Toolforge GridEngine to Toolforge Kubernetes.

Thanks, I merged it. Now could I delete https://github.com/Saisengen/wikibots/tree/main/php-tools ? Will you construct a build image, like on my tools? Should I run some building process now?

Mar 18 2024, 3:01 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

And webservice's error.log now contain only 200 responses, they should be written into access.log instead.

Mar 18 2024, 2:10 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

One of my continuous jobs runs on k8s, it fails with error, but it .err file doesn't updated, so I can't read what's the error. This problem begins today, earlier .err file worked correctly, maybe something with redirecting error stream to file is broken?

Mar 18 2024, 1:07 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T359529: Future of flaggedtemplates feature.

Let's try to understand each other. Ruwiki uses FR in this way: by default any page is displayed to everyone in the last version. Very small number of pages (<0.1% of all articles) is "stabilized": it means, anons and users with this setting see last reviewed version of page (and, probably, templates and files on it). Also, when user uses popups on internal links (default WMF extension), pop-up always contains last reviewed version of page, regardless of user's status (anon or experienced user) and stabilized page or not. (This last behaviour may be need to be fixed to show last version on pop-ups, for example, if infobox template was renamed and bot-replaced in unpatrolled revisions of page, pop-up contain only old infobox name and nothing more instead of pop-up content).

Mar 18 2024, 11:41 AM · MW-1.43-notes (1.43.0-wmf.8; 2024-06-04), DBA, MediaWiki-extensions-FlaggedRevs

Mar 16 2024

MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

This bots has also a strange issue: they write messages about correct working into error stream, see contents of files techtasks.err, autopurge-daily.err for example. This messages should be redirected to .out stream, and .err files should contain only messages about crashes.

Mar 16 2024, 6:14 AM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

validation-stats.err:

WARNING: /workspace/scripts/../facenapalmscripts/validstats.py:78: DeprecationWarning: datetime.datetime.utcnow() is deprecated and scheduled for removal in a future version. Use timezone-aware objects to represent datetimes in UTC: datetime.datetime.now(datetime.UTC).
  stats.append(datetime.strftime(datetime.utcnow(), "%Y-%m-%d"))
Mar 16 2024, 6:10 AM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

New errors on autopurge-daily:

WARNING: API error protectedpage: This page has been protected to prevent editing or other actions.
Traceback (most recent call last):
  File "/workspace/facenapalmscripts/autopurge.py", line 77, in process_null
    temp.touch()
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/page/_basepage.py", line 1424, in touch
    self.save(summary=summary, watch='nochange',
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/page/_basepage.py", line 1276, in save
    self._save(summary=summary, watch=watch, minor=minor, botflag=botflag,
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/page/_decorators.py", line 55, in wrapper
    handle(func, self, *args, **kwargs)
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/page/_decorators.py", line 46, in handle
    raise err
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/page/_decorators.py", line 35, in handle
    func(self, *args, **kwargs)
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/page/_basepage.py", line 1288, in _save
    done = self.site.editpage(self, summary=summary, minor=minor,
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/site/_decorators.py", line 86, in callee
    return fn(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/site/_apisite.py", line 2113, in editpage
    raise exception(page) from None
pywikibot.exceptions.LockedPageError: Page [[ru:Википедия:ИИ]] is locked.
Mar 16 2024, 6:08 AM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Yeah, this tool works now.

Mar 16 2024, 2:14 AM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319676: Migrate dibot from Toolforge GridEngine to Toolforge Kubernetes.

https://github.com/Saisengen/dmitry89-tools

Mar 16 2024, 2:05 AM · Grid-Engine-to-K8s-Migration

Mar 15 2024

MBH added a comment to T319676: Migrate dibot from Toolforge GridEngine to Toolforge Kubernetes.

Is there a way to move these files to the new repo, or I should re-create all of these files manually again?

Mar 15 2024, 1:36 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319676: Migrate dibot from Toolforge GridEngine to Toolforge Kubernetes.

I added all of them to https://github.com/Saisengen/wikibots/tree/main/php-tools. If it's needed to add html/css/js files from Dmitry's folder - say me or add yourself by pull.

Mar 15 2024, 12:48 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319676: Migrate dibot from Toolforge GridEngine to Toolforge Kubernetes.

I will publish them after my working day, but you can edit this php files directly in the Toolforge folder, they aren't binaries like my tools.

Mar 15 2024, 12:30 AM · Grid-Engine-to-K8s-Migration

Mar 14 2024

MBH updated subscribers of T319676: Migrate dibot from Toolforge GridEngine to Toolforge Kubernetes.

I was wrong: all of his php web tools doesn't work, looks like some refactoring are needed. @dcaro could you see?

Mar 14 2024, 3:56 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Thanks for explanation. user being casted to char because otherwise non-Latin usernames can't be read correctly.

Mar 14 2024, 3:08 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

I would recommend splitting it into different envvar variables for ease of usage and maintenance (so it would not be multiline).

Turns out I need only one secret for web tools: replica DB connection string, so I created a single-line envvar CONN_STRING, excluded it from test (I'm planning not to delete this tool) and deleted multi-line envvar CREDS created earlier from my password file. Non-web bots will still use password file, they need multiple strings from it.

Mar 14 2024, 2:30 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

After transition to k8s, a process of reading data from DB replicas was changed: now I got type errors when reading fields that I earlier read as strings. In one case, now field can't be read as string, it should be read as int, and I changed reading method. In another case I got error Can't convert byte[] to string when reading one text field, but another text field successfully reads as string. I found a way to convert that byte stream into string, but I'm interesting why this errors appeared after transition to k8s and why "username" field can be read as string, like earlier, but "action type" field should be read as byte stream now ("action type" field, unlike username, will contain only ASCII-7 characters and can contain only three values: "approve", "approve-i" or "unapprove"). I'm talking about this tool https://github.com/Saisengen/wikibots/blob/main/web-services/patstats/patstats.cs , see it today's changelog.

Mar 14 2024, 2:03 PM · Grid-Engine-to-K8s-Migration
MBH changed the status of T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes from Declined to Resolved.

We are in process of migration and some scripts works now, so I think this will be more correct status.

Mar 14 2024, 1:25 PM · Grid-Engine-to-K8s-Migration
MBH changed the status of T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes from Declined to Resolved.

We are in process of migration and we almost completed it, so this status will be more correct.

Mar 14 2024, 1:13 PM · Grid-Engine-to-K8s-Migration

Mar 13 2024

MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

You could open any page you have questions about just by entering its title into search field on ruwiki and clicking Enter. "К" is a ruwiki's alias for Категория (Category) namespace.

Mar 13 2024, 6:00 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

I don't know how to find out if it purged any pages.

Mar 13 2024, 5:53 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

It, obviously, https://ru.wikipedia.org/wiki/К:Википедия:Страницы_с_ежечасно_очищаемым_кэшем and https://ru.wikipedia.org/wiki/Шаблон:Очищать_кэш/статус

Mar 13 2024, 5:50 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

It (English) name means it purges pages, i.e. did null edits, so its edits will not be seen in its contribs. Its code written on Python, not Russian, so you can understand it better than me.

Mar 13 2024, 5:38 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

A file autopurge-hourly.err contains this error many times (since we revitalised this bots), so I assume it can be related to bot code. Maybe some outdated login method?

Mar 13 2024, 5:13 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

But one bot still has this error:

Traceback (most recent call last):
  File "/workspace/facenapalmscripts/autopurge.py", line 83, in <module>
    main()
  File "/workspace/facenapalmscripts/autopurge.py", line 78, in main
    respond.append(KEYS[arg](site))
                   ^^^^^^^^^^^^^^^
  File "/workspace/facenapalmscripts/autopurge.py", line 33, in process_hourly
    return "срочных: " + process_purge(site, "К:Википедия:Страницы с ежечасно очищаемым кэшем")
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/facenapalmscripts/autopurge.py", line 27, in process_purge
    if not site.purgepages(members[i:i+limit]):
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/site/_apisite.py", line 2897, in purgepages
    result = req.submit()
             ^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/data/api/_requests.py", line 993, in submit
    response, use_get = self._http_request(use_get, uri, body, headers,
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/data/api/_requests.py", line 684, in _http_request
    response = http.request(self.site, uri=uri,
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/comms/http.py", line 283, in request
    r = fetch(baseuri, headers=headers, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/comms/http.py", line 457, in fetch
    callback(response)
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/comms/http.py", line 333, in error_handling_callback
    raise ServerError(response)
pywikibot.exceptions.ServerError: HTTPSConnectionPool(host='ru.wikipedia.org', port=443): Read timed out. (read timeout=45)
CRITICAL: Exiting due to uncaught exception ServerError: HTTPSConnectionPool(host='ru.wikipedia.org', port=443): Read timed out. (read timeout=45)
Mar 13 2024, 5:05 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

If Skipped '/workspace/user-config.py': owned by someone else. isn't an issue, I don't see problems now on three bots.

Mar 13 2024, 5:03 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

I started to trying to rewrite my tools on January and did some work, looks like new code should be something like this:

var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();
Mar 13 2024, 4:52 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

If you could rewrite any one of my tools to follow modern dotnet way to build web apps, it will be very helpful to me and I think I will rewrite all other tools, looking by tool you rewritten. For example, https://github.com/Saisengen/wikibots/blob/main/web-services/likes/likes.cs , it's very tiny tool for 70 loc containing DB replica requests, it's almost all I use in my web tools.

Mar 13 2024, 4:42 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

One ruwiki user on our discord server noticed this change on your first PR, it looks like syntax error:

image.png (330×491 px, 18 KB)

This file: https://github.com/wikisaurus/wikisaurusbot/blob/master/facenapalmscripts/validstats.py

Mar 13 2024, 4:06 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

Merged, rebuilded, loaded. Current errors in two tools:

NameError: name 'latest_revision' is not defined
CRITICAL: Exiting due to uncaught exception NameError: name 'latest_revision' is not defined
Skipped '/workspace/user-config.py': owned by someone else.
Traceback (most recent call last):
  File "/workspace/facenapalmscripts/sandbox.py", line 49, in <module>
    main()
  File "/workspace/facenapalmscripts/sandbox.py", line 38, in main
    delta = time - page.latest_revision.timestamp()
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'Timestamp' object is not callable
CRITICAL: Exiting due to uncaught exception TypeError: 'Timestamp' object is not callable
Traceback (most recent call last):
  File "/workspace/facenapalmscripts/autopurge.py", line 83, in <module>
    main()
  File "/workspace/facenapalmscripts/autopurge.py", line 78, in main
    respond.append(KEYS[arg](site))
                   ^^^^^^^^^^^^^^^
  File "/workspace/facenapalmscripts/autopurge.py", line 33, in process_hourly
    return "срочных: " + process_purge(site, "К:Википедия:Страницы с ежечасно очищаемым кэшем")
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/facenapalmscripts/autopurge.py", line 27, in process_purge
    if not site.purgepages(members[i:i+limit]):
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/site/_apisite.py", line 2897, in purgepages
    result = req.submit()
             ^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/data/api/_requests.py", line 993, in submit
    response, use_get = self._http_request(use_get, uri, body, headers,
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/data/api/_requests.py", line 684, in _http_request
    response = http.request(self.site, uri=uri,
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/comms/http.py", line 283, in request
    r = fetch(baseuri, headers=headers, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/comms/http.py", line 457, in fetch
    callback(response)
  File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pywikibot/comms/http.py", line 333, in error_handling_callback
    raise ServerError(response)
pywikibot.exceptions.ServerError: HTTPSConnectionPool(host='ru.wikipedia.org', port=443): Read timed out. (read timeout=45)
CRITICAL: Exiting due to uncaught exception ServerError: HTTPSConnectionPool(host='ru.wikipedia.org', port=443): Read timed out. (read timeout=45)
Mar 13 2024, 3:33 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

My building process was just clicking on green arrow on Visual Studio panel, my "the tools installed that you used during the build" was just plain free (as in "free beer") Visual Studio regardless of its version (2016 or 2019 or 2022...), my deployment process was just compiling this programs like my non-web bots (that still runs on mono on k8s), moving it to Toolforge and renaming .exe to .cgi (the last one was tiring, yeah). The tiny little problem is that now I have absolutely no idea how this building process works, how works all these .sh files and can't fix anything without asking the developers. And if you become inactive for any reason, will any other developer understand and fix this process? Earlier I was able to solve almost all problems with these tools myself, now I can't solve anything and forced to ask here about any little issue because I doesn't understand how this, excuse me, Goldberg machine works.

Mar 13 2024, 3:20 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

Current error:

Traceback (most recent call last):
  File "/workspace/facenapalmscripts/sandbox.py", line 49, in <module>
    main()
  File "/workspace/facenapalmscripts/sandbox.py", line 38, in main
    delta = time - latest_revision.timestamp()
                   ^^^^^^^^^^^^^^^
NameError: name 'latest_revision' is not defined
CRITICAL: Exiting due to uncaught exception NameError: name 'latest_revision' is not defined

Looks like my fixing of 38th line was wrong, it's needed to define/construct latest_revision before calling its method, but I have no experience in Pywikibot and even Python and can't do it now (should read the docs), maybe you know how to solve this?

Mar 13 2024, 2:52 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.
Sleeping for 8.4 seconds, 2024-03-13 14:25:06
Page [[Обсуждение Википедии:Песочница]] saved
Sleeping for 9.5 seconds, 2024-03-13 14:25:15
Page [[Инкубатор:Песочница]] saved
Skipped '/workspace/user-config.py': owned by someone else.
WARNING: /workspace/facenapalmscripts/sandbox.py:38: FutureWarning: pywikibot.page._basepage.BasePage.editTime is deprecated since release 8.0.0; use latest_revision.timestamp instead.
  delta = time - page.editTime()

A script partially worked and partially not. I fixed 38th line and recompiled project, but doesn't know how to solve owning issue on /workspace/.

Mar 13 2024, 2:39 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

I tried to rewrite my tools using standard dotnet way to create web tools, but stuck on first steps.

Mar 13 2024, 2:33 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

A sandbox job spams my mail every ~15 mins about its failures, it will be good to fix it.

Mar 13 2024, 1:52 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

you have to add mount: all and filelogs: true to the entry in jobs.yaml for the files to get created

It will be easier to use .err files like earlier, could you did needed edits?

Mar 13 2024, 1:00 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Thank you very much for revitalasing my web tools. Could you explain what you did? Are they still runned through mono? If yes, why they run on python image, on the other side?

Mar 13 2024, 12:55 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.
* Job 'sandbox' (cronjob) (emails: onfailure) had 3 events:
  -- Pod 'sandbox-1710333455-mfbtf'. Phase: 'pending'. Container state: 'terminated'. Start timestamp 2024-03-13T12:37:37Z. Finish timestamp 2024-03-13T12:37:37Z. Exit code was '1'. With reason 'Error'. 
  -- Pod 'sandbox-1710333455-mfbtf'. Phase: 'failed'. Container state: 'terminated'. Start timestamp 2024-03-13T12:37:37Z. Finish timestamp 2024-03-13T12:37:37Z. Exit code was '1'. With reason 'Error'. 
  -- Pod 'sandbox-28505560-h7bcr'. Phase: 'failed'. Container state: 'terminated'. Start timestamp 2024-03-13T12:40:14Z. Finish timestamp 2024-03-13T12:40:14Z. Exit code was '1'. With reason 'Error'.

Sandbox process still fails, but it .err file doesn't updated.

Mar 13 2024, 12:52 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

Thanks. Could you did something to .yaml file on Toolforge updated automatically when GitHub file updated, or in process of building?

Mar 13 2024, 12:42 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

I followed both instructions and load jobs.yaml again. Let's see if bots will run...

Mar 13 2024, 12:31 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

One of scripts fails with this error:

Traceback (most recent call last):
  File "/data/project/wikisaurusbot/facenapalmscripts/sandbox.py", line 12, in <module>
    import pywikibot
ModuleNotFoundError: No module named 'pywikibot'
Mar 13 2024, 12:17 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T320164: Migrate wikisaurusbot from Toolforge GridEngine to Toolforge Kubernetes.

I have merged your patch and successfully built the image, what should we do now? I tried to load jobs.yaml and

tools.wikisaurusbot@tools-sgebastion-10:~$ toolforge-jobs load jobs.yaml
/usr/bin/toolforge-jobs:15: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html from pkg_resources import load_entry_point
Mar 13 2024, 12:15 PM · Grid-Engine-to-K8s-Migration

Mar 12 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

are you sending a newline at the end of your POST data?

First time I didn't add it, now I add it and tool freezes too.

Mar 12 2024, 5:03 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

And what the difference between TOOL_REPLICA and TOOL_TOOLSDB envvars? They are equal now for my tool.

Mar 12 2024, 4:44 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Remind me, how to rebuild only one tool? Will it be faster than rebuilding all tools and will other tools remain in image after that?

Mar 12 2024, 3:59 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Thanks, looks like it works now (I still have some questions. but will ask them later).

Mar 12 2024, 1:52 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Thanks. I merged your patch, successfully built all projects, stopped and started webservice (buildservice mount=all) and now all tools is inaccessible with ERR_EMPTY_RESPONSE or No webservice.

Mar 12 2024, 1:27 PM · Grid-Engine-to-K8s-Migration

Mar 11 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Thanks. But I added clusters5 and test to all.sln, replaced .csproj of both projects with code from your last message, runned building and it failed with the same error.

Mar 11 2024, 6:04 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

OK, that's what I know about all of this now.

Mar 11 2024, 5:06 PM · Grid-Engine-to-K8s-Migration

Mar 10 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

OK, I have solved most of errors, but got new. I have added last 5 tools to all.sln manually

run building and got this

[step-build] 2024-03-10T14:40:31.167168720Z Script ./compile.sh handling the post-update-cmd event returned with error code 1
[step-build] 2024-03-10T14:40:31.175133748Z
[step-build] 2024-03-10T14:40:31.175211160Z [Error: Failed to install dependencies]
[step-build] 2024-03-10T14:40:31.175231152Z Dependency installation failed!
[step-build] 2024-03-10T14:40:31.175234821Z
[step-build] 2024-03-10T14:40:31.175238924Z The 'composer install' process failed with an error. The cause
[step-build] 2024-03-10T14:40:31.175242196Z may be the download or installation of packages, or a pre- or
[step-build] 2024-03-10T14:40:31.175244954Z post-install hook (e.g. a 'post-install-cmd' item in 'scripts')
[step-build] 2024-03-10T14:40:31.175248276Z in your 'composer.json'.
[step-build] 2024-03-10T14:40:31.175250938Z
[step-build] 2024-03-10T14:40:31.175253559Z Typical error cases are out-of-date or missing parts of code,
[step-build] 2024-03-10T14:40:31.175256277Z timeouts when making external connections, or memory limits.
[step-build] 2024-03-10T14:40:31.175258681Z
[step-build] 2024-03-10T14:40:31.175261938Z Check the above error output closely to determine the cause of
[step-build] 2024-03-10T14:40:31.175264691Z the problem, ensure the code you're pushing is functioning
[step-build] 2024-03-10T14:40:31.175267344Z properly, and that all local changes are committed correctly.
[step-build] 2024-03-10T14:40:31.175269779Z
[step-build] 2024-03-10T14:40:31.175272474Z For more information on builds for PHP on Heroku, refer to
[step-build] 2024-03-10T14:40:31.175282592Z https://devcenter.heroku.com/articles/php-support
[step-build] 2024-03-10T14:40:31.177132777Z ERROR: failed to build: exit status 1
Mar 10 2024, 2:44 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

OK, I guessed, I should use webservice buildservice start --mount all instead of just webservice start.

Mar 10 2024, 11:17 AM · Grid-Engine-to-K8s-Migration

Mar 9 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Thank you very much, but it doesn't solve some of errors.

Mar 9 2024, 3:52 AM · Grid-Engine-to-K8s-Migration

Mar 7 2024

MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

No, the problem persists: now three tools you initially added to .sln file works, and ~seven new, added by you to sln later - responds with No webservice.

Mar 7 2024, 6:07 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Works now, may be a random failure.

Mar 7 2024, 5:49 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

Hmmm, now both links https://mbh.toolforge.org/cgi-bin/cpf and https://mbh.toolforge.org/cgi-bin/category-pathfinder responds with

image.png (158×647 px, 20 KB)

Mar 7 2024, 5:49 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

For static files, you can still use your public_html folder, but you'll have to access it through tools-static

And will my tools be able to read this file from new folder? They contains code like this: var reader = new StreamReader("elections.txt");, and elections.txt file is just on old public_html folder. Should I move it to folder pointed by you, and will tools read it from new folder?

Mar 7 2024, 5:28 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

it will not use anything from the NFS anymore

And only one working way to put something into my public_html (I mean not NFS folder, but a space, visible from the Internet on my subdomain on Toolforge) is now from GitHub? Earlier I sometimes generate a new version of data file for cluster analysis of ruwiki's elections and just move it to my public_html folder on Toolforge (several web tools reads this file). And sometimes I put a big .txt files for ruwiki to my public_html folder. Should I now add all updates of this files to GitHub and create an image with its new versions every time? If yes, it will be great if you improve compiling script to add all .txt files from my GitHub root folder and add them to image.

Mar 7 2024, 4:25 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

I did it

tools.mbh@tools-sgebastion-10:~$ toolforge webservice restart
Restarting..............................
Your webservice is taking quite while to restart. If it isn't up shortly, run a 'webservice stop' and the start command used to run this webservice to begin with.
tools.mbh@tools-sgebastion-10:~$ toolforge webservice restart
Restarting......................

After that I did ws stop and ws start.
Before that, I renamed category-pathfinder project to cpf and fixed a path to executable in html form, and fixed project name in all.sln. After that

Mar 7 2024, 4:15 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T319883: Migrate mbh from Toolforge GridEngine to Toolforge Kubernetes.

I might not have time to help you tweak the build script or might take me a while to get to it, specially if it's not blocking anything.

I understand it. I really appreciate you spending a lot of time to help me deal with my very specific case.

Mar 7 2024, 1:46 PM · Grid-Engine-to-K8s-Migration
MBH added a comment to T334940: All Graphs broken on Wikimedia wikis (due to security issue T336556).

+1000 to Michgrig (T334940#9610946)

Mar 7 2024, 12:50 PM · User-zeljkofilipin, Regression, User-notice, Tech Ambassadors & Translators, MediaWiki-extensions-Graph