I try cpu: 0.25 and it works. Thank you.

@Raymond_Ndibe Thank you for the response. Although I didn't specify the number of CPUs, I checked the quota. It seems that the quota is not enough because of the number of tasks, not a problem of not specifying the number of CPUs.

signature-check is a different tool? Can you open a task for it if so?

This will allow the robots to perform safely:

I checked the other tools and found that some of them need to increase quota:

@taavi Thank you for your help. The anchor-corrector looks good now. I will try others.

@taavi I initially intended to execute the three tasks sequentially. However, I later realized that `wait’ is not suitable for this purpose. Consequently, I had to request an increase in the quota for Cron jobs because I encountered limitations on the allowed number of Cron jobs.

@taavi I think the reason is that wait has a timeout of 5 minutes. So it can't be used in combination for long tasks. Please help me to set up 8 Cron jobs at the same time, thank you.

@taavi Sorry, could you please help me to see if it is because of my configuration that k8s-20201008.fix-anchor.archives.simple will not wait for k8s-20201008.fix-anchor.archives.en?

@taavi Thank you! I can run these jobs entirely.

@taavi Can you help me increase the limit for continuous jobs? The current quota is clearly not enough.

# toolforge-jobs load ~/wikibot/wikitech/toolforge-jobs-${USER/tools./}.yml
ERROR: Error: Invalid job k8s-20201008.fix-anchor.simple: Out of quota for this kind of job. Please see https://w.wiki/6YLP for details.

@taavi Will we accept longer IDs? Or do I have to shorten it?

@taavi Is this problem due to CPU limit?

Thank you for your help! However, I'm getting this error when I run it.
I thought the CPU quota limit was supposed to be a single task limit, maybe I'm wrong?

@taavi So I think I need to increase the quota for running continuous tasks...

@komla I want this task to run continuously, so I removed the schedule setting and left continuous: true. As for the last three tasks, they are set to run on a schedule. For my purposes, is this seems to be an appropriate setting?

Thank you! I changed the settings so it now looks like I need to increase the number of continuous jobs.

In T350484#9304982, @taavi wrote:

8+24Gi

Just to confirm: you mean up to 32Gi of total memory at the same time, with up to 6Gi for an individual job, right?

Yes, please help me to increase the memory capacity limit, thank you.

This is my current configuration, maybe you can see if it fits?

@nskaggs @komla @Aklapper And I also need to use more memory, maybe 16*8GiB per tool... It would be nice to have the latest node image versions (e.g. node20, node21) and keep up with the times.

@nskaggs @komla May I increase the number of Kubernetes pods running at the same time? Actually, the old 16 is not enough, so I split it into 4+1 tools...

Thank you!

@abi_ fixed.

@abi_ Hi. I find that https://gerrit.wikimedia.org/r/c/translatewiki/+/760557 says the file is not using utf-8. I can change the encoding. Should I do this?

Thank you. I will practice this method.

Also please provide access to the translatewiki bot to commit changes the master branch.

Should we commit translations to the master branch?

Yes, I expected translatewiki to commit to https://github.com/kanasimi/CeJS/tree/master/application/locale/resources/i18n
Or do we have any other way to update?

Yes. This seems more reasonable. :)

Oh, thank you for reminding. I just update the i18n data, you may find it https://github.com/kanasimi/wikiapi/tree/master/i18n .

Thank you.

For Chinese wiki, we have at least 2 conversions: traditional Chinese and simplified Chinese. Till now, the section anchor only works on exactly the same characters of the section title. I think it will be a good idea to let the section link also works on different conversions. However, it maybe needs a new design.

@bd808 Thank you.

@bd808 thank you for explaining the reason. May I increase the limit?

The situation occurs again. Perhaps the resource of grid engine is not enough? So we must waiting?

It seems going back to normal.

It passed some tasks just now. So it's not just my problem?

@Aklapper Yes, it's about Toolforge.

Tools like qstat-full also missed.

Thank you. Done.

OK. It is done.

I am sorry that it seems there are some bugs in my script. I have change some codes and trying to fix the problem.
Please call me anytime if there are still any bugs. Thank you.

I meet the same question. The page.page_latest is not the latest revision id of a page in Tool Labs database replication. May I get the latest revision id of all pages in one operation?