OmegaT - multiplatform CAT tool / Bugs / #847 Team projects not saving properly or stopping synchronization

Description has changed:

Diff:

--- old
+++ new
@@ -1,4 +1,4 @@
-Seems like the problem described in bug #836 still persists (segments in team projects not getting saved properly). Luckily we've lost only one segment out of 350, so this really only happens during autosave (set to 60 mins).
+Seems like the problem described in bug [#836] still persists (segments in team projects not getting saved properly). Luckily we've lost only one segment out of 350, so this really only happens during autosave (set to 60 mins).

 At the same time my client stopped updating segments updated in other clients. They were still showing as unedited, but once I tabbed into them, they were translated (so the issue has been reversed for these). Unfortunately I don't have a log for these two instances though.

Bugs: ~~#836~~

Didier Briel - 2017-01-09

assigned_to: Alex Buloichik

Group: None --> 4.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Didier Briel - 2017-09-14

assigned_to: Alex Buloichik --> nobody
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Didier Briel - 2017-09-14

Can you still reproduce it?

Didier

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Didier Briel - 2017-09-14

status: open --> pending
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Kos Ivantsov - 2017-09-18
  
  I just got report about 15 segments lost in our pt_BR L10N project. OmegaT 4.1.2_1 is used by all localisers.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Didier Briel - 2017-09-18
    
    Can you check the local logs to try to understand what happened?
    
    Didier
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mario Liebisch - 2017-09-14

Will try once we get the next bigger file for the project.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Didier Briel - 2017-09-18

status: pending --> open
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Roman Mironov - 2017-12-16

Tracked an instance of this error. Sending the information to Didier.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Didier Briel - 2017-12-16
  
  Thank you for the information. I'm not sure it's directly related (i.e., you do have lost translations, but there isn't similar errors in the log).
  
  Didier
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Roman Mironov - 2018-01-30

I faced this erorr again today. No errors in the log. But I noticed this issue: https://yadi.sk/i/lztDNX-83RvAMy

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Didier Briel - 2018-01-30
  
  Are the revision numbers (in the file names) and the timestamp of the files related to the recent issue?
  
  I'm asking, because I do have these files left from time to time, but, in my case, it's not related to loss of translations.
  
  Didier
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Mario Liebisch - 2018-01-30
    
    They're always there for us, even if the issue doesn't appear. Same for duplicates in the glossary sub directory. From my experience, edits are still only lost if you edit something while an automatic save happens. Therefore we've set auto saves to 60 minutes and we're no longer losing segments (at least not at an excessive rate), but we still get far more leftover files than lost segments.
    
    For reproduction: If possible, try throttling your upload so you can edit a few segments while auto-saving is in progress.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Roman Mironov - 2018-01-31
    
    I don't think so.
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Damien Rembert - 2018-03-23

[EDIT] not the same issue, but not deleting my post as it might delete the replies that followed.

Same issue here and I was wondering if it might have to do with the TMX merging operation?
I never see the window in which you're asked to pick translations when there are differences between segments in the local and remote project_save.tmx.

I'm using Omegat 4.1.3_2 without JRE on Windows. I also get lots of "tmx#oldbased" files

Last edit: Damien Rembert 2018-03-23

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Didier Briel - 2018-03-23
  
  I never see the window in which you're asked to pick translations when there are differences between segments in the local and remote project_save.tmx.
  
  As far as I know, this window is only supposed to appear if there is a real conflict: i.e., two translastors have translated the same segment differently during the last save period.
  
  Didier
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
  - Mario Liebisch - 2018-03-23
    
    Exactly. It's not really related to conflicts (whether they appear or not). From my observations the actual problem is OmegaT will simply ignore all changes to segments while uploading changes. This is a non-issue and possibly even almost impossible to track with fast internet, but if you're stuck at less than 1 mb/s upstream and the translation memory for the current project is reasonably sized, you'll potentially lose notable amounts of work, especially if you're running the default 3 minutes autosave window.
    
    Due to this we basically disabled auto-saving by setting it to an hour, which is sad but the only realistic way to actually keep working with OmegaT, even though it means we're losing the ability to collaborate in "real time".
    
    If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
    - Didier Briel - 2018-03-23
      
      So, based on your experience, the lost segments are lost when typing during the upload?
      
      Didier
      
      If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
      - Mario Liebisch - 2018-03-23
        
        If I edit something while saving/uploading is in progress, chances are high I'm losing those segments, correct. We haven't lost a single segment in 20 or 30k words if we're not using auto-saving and instead save while doing something else or taking a break.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Didier Briel - 2018-03-23
        
        How long does the save/upload process take for you?
        
        Didier
        
        Last edit: Didier Briel 2018-03-23
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Mario Liebisch - 2018-03-23
        
        Hard to tell, can easily be a minute or two due to crappy upstream, but it even happens for my co-worker who's got like 10 mpbs up but a slower cpu, so hard to tell at which point something is lost.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Damien Rembert - 2018-03-23
        
        Would it be possible to separate local saving and git/SVN?
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Didier Briel - 2018-03-23
        
        Theoritically, yes.
        
        But I feel it would be a bit of a pity to invest time and energy in that instead of solving the issue.
        
        Didier
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
        
        Mario Liebisch - 2018-03-23
        
        Would it be possible to measure the time it takes to save/upload and then notify the user in case this is a significant portion of the auto save intervall? While this wouldn't fix the issue, it might be helpful because even if you're not losing segments, usage sometimes might feel rather sluggish while saving.
        
        If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Team projects not saving properly or stopping synchronization

The free computer aided translation (CAT) tool for professionals

Group

Searches

Help

#847 Team projects not saving properly or stopping synchronization

Related

Discussion

Related