Page MenuHomePhabricator

Translate error - unable to save translations on metawiki in one page just marked for translation
Open, HighPublic

Description

[UPDATE] This is an erratic bug. If you encounter it, there are a few potential workarounds:

  • just wait a few minutes before trying, and it should un-stick itself as the jobqueue catches up
  • or re-mark the page for translation: Make a dummy edit (i.e. add or remove an empty line) on the source page. Mark for translation. Wait a few seconds. Now resuming translations should work.
  • or play with Special:AggregateGroups,
  • or ask a person with server access to run the Translate/scripts/createMessageIndex.php script.

[Original task description. Initial example has fixed itself.]
When I try to add a translation, or change an existing translation, I get the error Saving the translation failed: This namespace is reserved for content page translations. The page you are trying to edit does not seem to correspond any page marked for translation.
at https://meta.wikimedia.org/w/index.php?title=Special:Translate&group=page-Global+Reach%2FAnnouncements%2FBahasa+Indonesia+Search+Pilot+FAQ&action=page&filter=&language=id

I've tried using "remove from translation" and re-setting it, but that didn't fix it.

There was an earlier user-error where translation-markers were manually added, but I've never seen that issue lead to this problem before.

Event Timeline

Quiddity created this task.Apr 16 2019, 5:32 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 16 2019, 5:32 PM

Nikerabbit says (despite being on sickleave!)

might be an issue with jobqueue or an issue with jobs with details on logstash

abi_ added a subscriber: abi_.Apr 17 2019, 4:34 AM
Elitre added a subscriber: Elitre.Apr 17 2019, 10:16 AM

I'm getting that too while trying to add localised versions of the infographic to the various (still empty) translations of https://meta.wikimedia.org/wiki/Affiliate-selected_Board_seats/2019/Primer_for_user_groups .

Elitre added a subscriber: Arrbee.Apr 17 2019, 1:56 PM

As an update, @Arrbee: I have now managed to do the edit I wanted on the French and Arabic pages. Before attempting I did a dummy edit on the English version. Will keep you posted and LMK if you need to know anything.

abi_ added a comment.Apr 17 2019, 9:37 PM

I've been able to reproduce the problem. Saving translations for any new text that's been added to the page fails to save with the given error. Like @Elitre mentioned, if I edit a translation unit / text on the English page, and then go back and try to translate the message, things work again. I did not face this issue while saving translations for existing translation units ( or text on the page).

Nikerabbit triaged this task as High priority.Apr 18 2019, 7:25 AM

We will continue investigating this and T213802: Investigate ways to reduce the size of translate-groups cache key and T203786: Mcrouter periodically reports soft TKOs for mc1029 (was mc1035, mc1022) leading to MW Memcached exceptions which may be related, but that will take a while due to availability issues. In my opinion this issue is high priority but not UBN!.

Summary

  • This issue is pretty similar to the previous cases where new pages (or new sections of existing pages) marked for translation are not immediately translatable.
  • There has always been a delay because it goes through a jobqueue. Usually this is just a few minutes.
  • Possibly due to recent changes, these job queue jobs seem to be failing occasionally. Maybe they also run slower now, but I don't have evidence for or against.
  • This issue is, at least for now, self-healing, that any later run will make the previously untranslatable sections translatable.

Workarounds

  • For urgent cases, to try to make new content translatable, one can (re-)mark any page for translation, or play with Special:AggregateGroups, or ask a person with server access to run Translate/scripts/createMessageIndex.php script.

Impact
New content is not immediately translatable. Delays are longer than usual and an increase of failures is seen in Logstash.

In my opinion this issue is high priority but not UBN!.

Agreed. Sorry I didn't followup on my IRC comment, where I suggested it might be! I wasn't sure how permanent this bug might be.

Talking of which, I should've mentioned that my original example in the task description has fixed-itself as of this morning, so yes, this is a temporary heisenbug (IIUC, or thereabouts) for now!

Workarounds

  • For urgent cases, to try to make new content translatable, one can (re-)mark any page for translation, or play with Special:AggregateGroups, or ask a person with server access to run Translate/scripts/createMessageIndex.php script.

Ah, cool, thanks for those tips :)

We will continue investigating this and T213802: Investigate ways to reduce the size of translate-groups cache key and T203786: Mcrouter periodically reports soft TKOs for mc1029 (was mc1035, mc1022) leading to MW Memcached exceptions which may be related, but that will take a while due to availability issues. In my opinion this issue is high priority but not UBN!.

Summary

  • This issue is pretty similar to the previous cases where new pages (or new sections of existing pages) marked for translation are not immediately translatable.
  • There has always been a delay because it goes through a jobqueue. Usually this is just a few minutes.
  • Possibly due to recent changes, these job queue jobs seem to be failing occasionally. Maybe they also run slower now, but I don't have evidence for or against.
  • This issue is, at least for now, self-healing, that any later run will make the previously untranslatable sections translatable.

    Workarounds
  • For urgent cases, to try to make new content translatable, one can (re-)mark any page for translation, or play with Special:AggregateGroups, or ask a person with server access to run Translate/scripts/createMessageIndex.php script.

    Impact New content is not immediately translatable. Delays are longer than usual and an increase of failures is seen in Logstash.

ASBS translations are going to be quite urgent for the next couple of weeks. I myself may not be around all the time to check that people aren't having issues there or to help them figure out the workaround.

I understand if this can't be solved immediately, and I appreciate details (like step-by-step) around the various workarounds so that at least everyone will know what can be done until then.

Nemo_bis renamed this task from Translate error - unable to save translations on metawiki in one page to Translate error - unable to save translations on metawiki in one page just marked for translation.Apr 18 2019, 10:29 AM

This is the easy workaround I'm aware of:
Make a dummy edit (i.e., add or remove an empty line) on the source page. Mark for translation. Now resuming translations should work.

Please document others with steps if you know what they look like. TY!

Quiddity updated the task description. (Show Details)Apr 19 2019, 5:21 PM
Eihel added a subscriber: Eihel.Apr 23 2019, 6:11 PM

Hello, I submit my comments that I found on Meta [[ URL | https://meta.wikimedia.org/w/index.php?title=Meta:Requests_for_translation_adminship/Eihel&type=revision&diff=19037860&oldid=19036317&diffmode=source]]:

Hello, my observations @Aldnonymous:
First, the page I was dealing with, is not done the right way with the <translate> tags (multiplication of translation). The translation could be done even with a different text version. But Wladek92 has changed the layout (with good reason), but without adding the markers of translation. The original text is visible, but is no longer available for translation, hence the message "The page you are trying to edit does not seem to correspond any page marked for translation". In addition, any translations made previously is no longer visible (as the marker is removed, the page page/language is lost) , that's what baffled me. I think the problem was to mark the version for translation with new markers <!--T:1--> (declare on Meta talk:Babylon or talk to Elitre (WMF)), which was not. Apparently, the bug only appeared later after this change. "there's possible work around afaik": yes, but only for pages with all markers and that's where I could be useful. I am not a aficionado of Phab, so if you want to go up the info, no problem. Greetings friendly. --Eihel (talk) 11:11, 23 April 2019 (UTC)

Follows T221119#5119115 T213802 T221119#5121833 (given by Aldnonymous)

Teles added a subscriber: Teles.Apr 25 2019, 12:37 AM
abi_ added a comment.Sat, Apr 27, 12:33 PM

Hello, I submit my comments that I found on Meta [[ URL | https://meta.wikimedia.org/w/index.php?title=Meta:Requests_for_translation_adminship/Eihel&type=revision&diff=19037860&oldid=19036317&diffmode=source]]:

Hello, my observations @Aldnonymous:
First, the page I was dealing with, is not done the right way with the <translate> tags (multiplication of translation). The translation could be done even with a different text version. But Wladek92 has changed the layout (with good reason), but without adding the markers of translation. The original text is visible, but is no longer available for translation, hence the message "The page you are trying to edit does not seem to correspond any page marked for translation". In addition, any translations made previously is no longer visible (as the marker is removed, the page page/language is lost) , that's what baffled me. I think the problem was to mark the version for translation with new markers <!--T:1--> (declare on Meta talk:Babylon or talk to Elitre (WMF)), which was not. Apparently, the bug only appeared later after this change. "there's possible work around afaik": yes, but only for pages with all markers and that's where I could be useful. I am not a aficionado of Phab, so if you want to go up the info, no problem. Greetings friendly. --Eihel (talk) 11:11, 23 April 2019 (UTC)

Follows T221119#5119115 T213802 T221119#5121833 (given by Aldnonymous)

Hi @Eihel

Thanks for reporting the problem that you are having. This problem does not seem like its related to this issue. You should be able to use the Special:PageMigration to retrieve the old translations. You can read more about how to use this tool here.

Please let me know if that helps and if you require further help.

Same here. I did this: https://meta.wikimedia.org/w/index.php?title=Global_sysops&diff=19079406&oldid=19001329

And tried to translate it to Dutch, but without luck. I thought I did something wrong, but I was told it is a bug... Please fix it, if you can.

Zppix added a subscriber: Zppix.Mon, May 6, 1:31 PM

Is there a fix foreseen in the future?

Nikerabbit added a comment.EditedMon, May 6, 3:42 PM

It's unclear what is the cause here. The symptoms are very clear (The page you are trying to edit does not seem to correspond any page marked for translation.), but there are many things that can break and cause this symptom. It is not easy to debug what is actually going on there, and the fact that the job queue is involved makes it a bit harder still to debug.

Further debugging is needed before a fix can even be attempted.

@Trijnstel @Zppix @Wladek92 +1 and similar comments don't help. As long as this task is opened, the bug is very likely to persist. We know about this issue and I believe the team behind MediaWiki-extensions-Translate are already working on this issue. This bug has workarounds available, see the task description. If the workarounds are unclear to you, feel free to ask!