@Pginer-WMF since triggering the Captcha dialog in production is tricky, can we close this task based on the screenshots I took in my dev envinroment? These screenshots were also shared inside the related patch, and I'm sharing them here, too:

@EChukwukere-WMF currently the retry MT card is only visible when an HTTP error occurs, which we cannot trigger on demand. I've submitted a new patch, so that the retry MT card also appears for network errors. When this is deployed, you can easily test the retry MT card by blocking the request URL that is used for sentence translation fetching. Moving this back to "In progress" for now.

@Pginer-WMF the message inside the dialog according to the task description says:

The recent refactoring has been completed after merging the last CX build. We do not plan to make any other refactoring soon. This task can be closed as completed.

@Pginer-WMF regarding this task, all subtasks listed in the task description have been completed. Only a few buttons are remaining to be replaced with Codex buttons inside Section Translation, but this is a very small portion of the effort required for this task, and can be tracked in another small task, once we decide to work on this again (which won't be too soon). I'm suggesting to close this task as done. Replacing the deprecated codex-search-styles module can be tracked in T360223, as Roan suggests above.

Noted! Sounds like an easy fix, maybe we can opportunistically fix that at some point.

Indeed, this task cannot be tested from the UI. I'll post the decrease in size for the Section Translation artifacts (JS build files), that "proves" the abandonment of Vue and Vuex npm modules. This task can be considered done.

This task has not been fixed. Moving this to backlog. I will also submit a screencast of the still existing issue, soon.

This issue has been fixed as demonstrated in the following screencasts:

The above screencast doesn't prove that the issue has gone, as it doesn't follow the logic/steps in the description. Moving this back to "Needs QA".

This task is not done. The above screencast doesn't demonstrate that draft/published translations are filtered from the dashboard suggestion list, it just demonstrates the "Refresh suggestions" feature. Moving this back to "In review" column, following the latest patch.

@EChukwukere-WMF The above screencast refers to an article translation using Content Translation. This task is about section translation using Content Translation, which is a different case. Moving this back to "Needs QA" column.

I cannot reproduce this issue. Probably the root cause has already been fixed. I'm sharing a screencast of the machine translation working properly for this article (en->bn translation in bn production wiki):

Content and Section Translation applications will not be affected by IP masking/temp users at this point. I also submitted a patch (check above) to make sure we do not check for anonymous users (only for named users), but this patch is mostly about consistency in our codebase, and visibility of some entrypoints that should only be visible to named users. Once this patch is merged, we can officially consider this task as done.

The fix is now deployed:

In T353734#9554211, @KartikMistry wrote:

@ngkountas Do we need to add target languages in wgSectionTranslationTargetLanguages for these Wikipedias?