Change Details

Yeah, that is my best attempt for title. The less cryptic explanation as follows: 1. Translator starts a translation T1. Translates sections T1-s1, T1-s2, T1-s3, T1-s4 2. Translator decides to delete this translation. Does so from CX dashboard. 3. Translator wants to translate T1 again from scratch. The newly started translation is T2 4. Translator translates 2 sections. T2-s1, T2-s2. Saves it 5. Translator returns and resumes T2. T2-s1, T2-s2 are restored as expected. In addition to this T1-s3, T1-s4 are also restored. That is wierd. Internally what happens is, T1, T2 get same translation id since its SourceLanguage-TargetLanguage-SourceTitle pair is same. With this translation Id, sections are stored in corpora table. When T2 started, we are not fetching this from table because it is a fresh translation. But when T2 is restored, All sections from corpora table which match the translation id is restored. They are T2-s1, T2-s2, T1-s3, T1-s4 So this is an edge case. When T2 started while T1 exist with deleted status, we probably want to clear sections associated with it from corpora table while doing deleted->draft transition. Or, does it help the translator by providing the old saved sections? (+cc @Pginer-WMF )

Yeah, that is my best attempt for title. The less cryptic explanation as follows: 1. Translator starts a translation t1. Translates sections t1-s1, t1-s2, t1-s3, t1-s4 2. Translator decides to delete this translation. Does so from CX dashboard. 3. Translator wants to translate t1 again from scratch. The newly started translation is t2 4. Translator translates 2 sections. t2-s1, t2-s2. Saves it 5. Translator returns and resumes t2. t2-s1, t2-s2 are restored as expected. In addition to this t1-s3, t1-s4 are also restored. That is wierd. Internally what happens is, t1, t2 get same translation id since its SourceLanguage-TargetLanguage-SourceTitle pair is same. With this translation Id, sections are stored in corpora table. When t2 started, we are not fetching this from table because it is a fresh translation. But when t2 is restored, All sections from corpora table which match the translation id is restored. They are t2-s1, t2-s2, t1-s3, t1-s4 So this is an edge case. When t2 started while t1 exist with deleted status, we probably want to clear sections associated with it from corpora table while doing deleted->draft transition. Or, does it help the translator by providing the old saved sections? (+cc @Pginer-WMF )

Yeah, that is my best attempt for title. The less cryptic explanation as follows: 1. Translator starts a translation T1t1. Translates sections Tt1-s1, Tt1-s2, Tt1-s3, Tt1-s4 2. Translator decides to delete this translation. Does so from CX dashboard. 3. Translator wants to translate Tt1 again from scratch. The newly started translation is T2t2 4. Translator translates 2 sections. Tt2-s1, Tt2-s2. Saves it 5. Translator returns and resumes T2t2. Tt2-s1, Tt2-s2 are restored as expected. In addition to this Tt1-s3, Tt1-s4 are also restored. That is wierd. Internally what happens is, T1t1, T2t2 get same translation id since its SourceLanguage-TargetLanguage-SourceTitle pair is same. With this translation Id, sections are stored in corpora table. When Tt2 started, we are not fetching this from table because it is a fresh translation. But when Tt2 is restored, All sections from corpora table which match the translation id is restored. They are Tt2-s1, Tt2-s2, Tt1-s3, Tt1-s4 So this is an edge case. When Tt2 started while T1t1 exist with deleted status, we probably want to clear sections associated with it from corpora table while doing deleted->draft transition. Or, does it help the translator by providing the old saved sections? (+cc @Pginer-WMF )