In T278211#6957950, @Curb_Safe_Charmer wrote:

@zhaofengli just this moment created a Curb Safe Charmer account on wikitech.wikimedia.org.

In T278211#6957860, @Curb_Safe_Charmer wrote:

@zhaofengli it is great to hear from you. It would be very helpful to have a controlled handover. So yes please on access. I have created a separate Github account for the purpose: https://github.com/CurbSafeCharmer

It seems to be that this problem is only affecting Refill when the language is set to en. All other languages appear to work fine. So I believe there's been a breaking change on en.wiki. The priority is to prove that this is the case, identify what the change was, and either address the issue at the Wikipedia end or amend the Refill code to deal with whatever has changed on en.wiki.

Hi all, somehow I missed the various notifications. I'm not active on Wikipedia anymore and my knowledge of the tool has faded over the years. From the first glance at the logs posted here I'm not able to see what the root cause is, and I'm logging into Toollabs today to see what's going on.

Hi all,

The fix is now live on Toolforge, and should be picked up by Translatewiki during the next sync.

An example would be http://nna-leb.gov.lb/ar/show-report/371/, from which Citoid extracts metadata containing UTF-8 replacement characters.

This isn't managed here, but since you asked, I've added arwiki with this commit. You can test the tool in Arabic here. Please use my talk page next time, thanks!

FYI, the hardcoded conversion table is includes/ZhConversion.php which may help determine the language variant of arbitrary text.

The relevant code is available here.

I cannot replicate this. What's the name of the page in question?

Since I don't think JuneHyeon Bae's working on this, I've made the patch. I hope JuneHyeon don't mind.

I've created https://secure.phabricator.com/T7309 to address the problem of scratch tokens.

@Aklapper Thanks, it's on P280.

If using the committed identity is acceptable, how can I send you the source text in a secure way?

No, I didn't see any one-time token when activating the feature. I can provide my committed identity on my enwiki user page (at the bottom) to prove my identity.

Echo sends the notification to the editor who made wpUndidRevision which is set by the tool used (Twinkle, etc).1 Maybe we can find a way to identify those pseudo-edits, and avoid sending notifications if it's the case. To achieve this, we can add a permanent flag like the minor flag to those edits. However, this also mean changing the database schema.

Okay, I think I've figured it out. While the best way to avoid this problem is to optimise the program, it's possible to increase the memory limit by creating a copy of /usr/bin/webservice and editing it.