Noticed while @Petar.petkovic reviewing https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/457410/
Here is the easy way to reproduce with going back to dashboard only once:
- Start fresh translation
- Translate one paragraph using Apertium and save ('Apertium' and 'source' entries are added to CX corpora and 20180911092929 is the timestamp)
- Switch to "Don't use MT" and save (entry for 'user' is added to CX corpora and timestamp is 20180911092949)
- Switch back to Apertium and save (previous 'Apertium' entry in the CX corpora does not update its timestamp, so 20180911092929 remains)
- Go back to dashboard and restore, to see blank section instead of one coming from Apertium
In 2016, to fix an issue related to database issue @Nikerabbit authored https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ContentTranslation/+/273886. That patch intenationally avoided updating timestamps when translation units are updated.
That patch has a comment : "Preventing the duplicates in the first place is left as an follow-up". Looks like time for that follow up is arrived