tedbot is now on Debian Bookworm.

Oh, I didn't realize I was still using the old buster bastion. Thanks for letting me know. I'll check out the migration guide and start transitioning to the newer one.

Thanks for the reboot — the issue seems to be resolved now. become is working properly again on login-buster.toolforge.org.
Appreciate the help!

Thanks for the update.
However, I'm still experiencing the issue. When I run the become command on login-buster.toolforge.org, it hangs and does not proceed. This seems to persist even after the outage has been resolved.
Could you please take another look when you get a chance? Happy to provide any additional details if needed. Thanks again!

Hi, unfortunately I'm encountering the same issue again. The become command is still not working properly on login-buster.toolforge.org, just like before.

Thanks so much, it's working perfectly now! Really appreciate your help and quick support.

The issue occurred because the mediawiki.ui.button did not load during the preview. I have no idea why the problem happened. As a workaround, you can try the following script:

I see no grid jobs, but the grid-deprecation page says that the job lighttpd-tedbot is still running.

@Dzahn @bd808 Thanks, I now see the ko_KR.utf8 in the list. :)

I don't have locale-gen command as it says "-bash: locale-gen: command not found."

Thanks for the confirmation, but I don't see the locale yet.

I've recently noticed that Korean locales are missing.

Thanks for the fix. Let me run your bot, check whether the issue is resolved and get back to you shortly.

I see, thanks for the reply. :) You may close this ticket.

@Framawiki Yes, I confirm that it is working fine. Thank you.

In T110509#3847424, @Aklapper wrote:

I wonder if https://www.mediawiki.org/wiki/ResourceLoader/Migration_guide_(users)#Keep_gadgets_central could be helpful.

If the problem still persists, the original author Endo999 should fix the issue first since the script is basically the same as https://en.wikipedia.org/wiki/User:Endo999/GoogleTrans.js.
Also, note that many local wikis such as enwiki, arwiki, simple, hawiki, hiwiki, srwiki, nlwiki, ptwiki, nowiki, sowiki, mswiki, eswiki, ukwiki, mkwiki, and zhwiki completely are based/depend on older or the latest version of it.

This issue was brought up over 2 months ago in Korean Wikipedia, and we are still waiting for the issue to be resolved in the near future.
Please understand that the "encapsulate" action is required in the VisualEditor because it has been frequently used in the source editor for a long time.

Thank you, Dzahn. It's working fine now.
I appreciate your quick support.

Sorry, but I still don't see the ko_KR.EUC-KR on the login.tools.wmflabs.org.

I've just opened a new session for testing, but I don't see the euckr when running locale -a.
Have you tried "dpkg-reconfigure locales" that I mentioned above after running the locale-gen?
That is because the locale-gen alone will not affect the environment globally without reboot, AFAIK.

Thanks for your help. ko_KR.utf8 could be found.
However, I still cannot find EUC-KR for my application. Could you consider to add it as well?

How long will it take for my request to be processed?
Please let me know if you need any additional information.

I can limit my request to the locales as follows:

• ko_KR.euckr : cp949 and its extension are compatible with this charset. My application depends on this charset.
• ko_KR.utf8 : For unicode compatibility.

Thanks, Krenair.
From now on I will follow your advice before creating a task.

No, I am talking about the login.tools.wmflabs.org.
According to the output from "locale -a", I don't find any Korean-related charsets.

I am using a Perl script that I created for TedBot on ko-wiki.
However, in the current circumstance, I won't be able to directly type Korean characters on the shell prompt.