Good news is it works, we started with 20k of mentees

Much better:

Since I already wrote the code here.

Note this was reverted because it didn't seem to be working, see https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/+/1244679.

It seems the job is timeouting:

Okay, the other issue should be now resolved, so I'm continuing the investigation here. I'll post an update as a comment.

Mission succeeded. The amount of reassignMenteesJob jobs should drop.

This is not the easiest patch to deploy... To be able to deploy it w/o merge conflicts, we need to pull a bunch of code refactors to production... Here is a list of patches to backport to wmf.16:

Thanks! Moving to Doing, I'll deploy it soon.

This should now be done. Growth features are now available on the following wikis:

This should now only need r239954 to get merged+deployed. Moving to Code Review.

Resolved by virtue of resolving the subtask.

Should be finally ready.

Fix attached

During investigating this issue, I found an (unrelated) issue that is currently tracked privately at T418222. The Growth-Team needs to fix the private issue first. I'll continue with this task as soon as I finish the other one.

Resolving.

Liu1126 resigned on December 16, 2025. Fortunately, we still have logs from then:

Thanks @Pppery for linking the prior task! Liu1126 indeed has quite a few mentees:

In estimation, we discussed how this task is related to T415647: Add "Create account" menu item to mobile web hamburger menu (since that task asks for a competing action, which might affect the experiment results). It would be great to get clarity from @KStoller-WMF (but I recognise she's currently unavailable).

Hi @Prototyperspective, thank you for the report! Would you mind providing more details, please (such as a screenshot)? I tested going to https://en.wikipedia.org/wiki/Special:Homepage on both my laptop and my mobile, and in both cases, I found topics from multiple categories. On the phone, I had to scroll down to see them, but they were present:

Attempting to save:

I tried deploying the force legacy validation patch today, and it failed, with:

Note this is impossible to verify without changing local CC configuration (you'd need to set the readValidationLogLevel option under a CommunityConfiguration provider and then introduce an invalid config to test this).