I see that RL update happened hours later deployment. ( https://twitter.com/wikimediatech/status/644732028240461824 ) and after that this issue fixed.

@greg, Is there a reason why the message updates not run just after deployment?

In T112964#1652403, @santhosh wrote:

I see that RL update happened hours later deployment. ( https://twitter.com/wikimediatech/status/644732028240461824 ) and after that this issue fixed.

@greg, Is there a reason why the message updates not run just after deployment?

l10nupdate happens once/day in the evening (SF time). It "has always been so" (since I've been here).

What is the issue, exactly? scap updates l10n messages that it has.

Is there a use-case for pulling messages from translatwiki more frequently than nightly?

In T112964#1658252, @greg wrote:

In T112964#1652403, @santhosh wrote:

I see that RL update happened hours later deployment. ( https://twitter.com/wikimediatech/status/644732028240461824 ) and after that this issue fixed.

@greg, Is there a reason why the message updates not run just after deployment?

l10nupdate happens once/day in the evening (SF time). It "has always been so" (since I've been here).

What is the issue, exactly? scap updates l10n messages that it has.

This makes sense, but it looks like what happened in this case is that scap didn't actually update all the L10n messages. The patches deployed in the train introduced several new messages. Several of them were shown as expected, but cx-translation-filter-suggested-translations was not.

Is there a use-case for pulling messages from translatwiki more frequently than nightly?

No, this is probably not the issue here. It looks like the L10n update in the scap that ran after the train didn't pick all the new messages. But I didn't investigate deeply - @Nikerabbit and @KartikMistry may have more precise details.

There wasn't any indication of a problem from scap, at least I didn't notice anything unusual.

I can reproduce this bug on https://pt.wikipedia.org/wiki/Especial:ContentTranslation (after enabling ContentTranslation beta from preferences).

• The message is sent to the client (e.g. not null), but with a fallback value produced by the server.

mw.messages.get('cx-translation-filter-suggested-translations');
> "<cx-translation-filter-suggested-translations>"

• The message is working fine in the server-side localisation cache.

$ mwscript eval.php --wiki ptwiki
> return wfMessage('cx-translation-filter-suggested-translations')->plain();
Sugestões
> return wfMessage('cx-translation-filter-suggested-translations')->inContentLanguage()->plain();
Sugestões
> return wfMessage('cx-translation-filter-suggested-translations')->inLanguage('en')->plain();
Suggestions

• The message is broken in MessageBlobStore.

ptwiki> SELECT * FROM msg_resource WHERE mr_resource='ext.cx.dashboard';

This sounds like T93800.

Now I see it in the English Wikipedia, where this feature was deployed yesterday in SWAT :/

https://en.wikipedia.org/wiki/Special:ContentTranslation

Add that to the duped bug to rise priority?