@KCVelaga_WMF should we just remove the last item (user clicks to (pre)view a wiki link**) from the task description?

@KCVelaga_WMF I approved the above patch to add the MinT translation provider, but since we are here, let's fix all the translation providers. According to the CX documentation the following MT providers are supported:

• MinT
• Apertium
• LingoCloud
• Google Translate
• Yandex
• Elia

@GMikesell-WMF yes, this task is QA testable. This is a task about instrumentation, so the easiest way to reproduce it, is to enable debug logs for each logged event inside your browser developer console, and also as popups inside your screen.

The last occurrence of this error was on August 29th, which is the day that the fix has been deployed to group2 wikis. Logstash search: https://logstash.wikimedia.org/app/discover#/?_g=h@7b5aa23&_a=h@9b739dd.

@GMikesell-WMF thank you for all the effort for this review. Sadly, this functionality is not related neither to ContentTranslation application, nor to Section Translation application. This task is about an API endpoint that is intended to be used inside the Automatic Translation application -aka MinT MVP for Readers. An example request to this endpoint is this: https://en.wikipedia.org/w/api.php?action=query&format=json&list=automatictranslationdenselanguages&continue=&formatversion=2&qid=Q100.

Thank you @KCVelaga_WMF!

If you ask me, none of the sources makes a lot of sense. content_language_selector, direct, and notification_deletion are all possible sources for the dashboard_open event, while dashboard_translation_continue and dashboard_translation_start are separate events, which means we can easily check if the user is coming to the editor ("Pick a sentence" step) by starting or continuing a translation, by checking the previous logged event (should be one of those two).

@KCVelaga_WMF The definition of the editor_open event and the possible event sources in the schema documentation, seems to be based on the Content Translation workflow.

I created a simple script to send 50 consecutive requests to the endpoint for this URL: /api/v1/translation/sections?source=en&target=el&seed=Grimes. In my local env, all 50 requests were successful. When I tried the same for the LiftWing production API, 10 out of 50 requests failed.

@ssingh sorry for the repeated mistake. I uploaded a different one that is not listed in idm.wikimedia.org keys. Thank you!

The dialog that blocks fast unreviewed translations shows up properly as demonstrated by the following screencast from greek (el) production wiki. NOTE: The dialog takes a while to show up, and we may need to add some kind of loading indicator. The loading time during the second time the dialog opens was cut off from the screencast and this is why it appears shorter. The actual time is much longer, like it is in the first time the "check unreviewed translation" dialog opens.

@eamedina it feels to me that this task is ready for QA. What do you think?