-
Bug
-
Resolution: Fixed
-
None
-
Critical
-
A new worker was introduced for pausing match analysis if t5memory is importing a file
-
Emptyshow more show less
problem
If a TMX import is running on a t5memory TM, it still could be used for fuzzy searches. This may crash the whole t5memory service.
solution
- For direct usage in a task: Before usage of fuzzy / search / update methods in connector, the status of the TM should be checked first.
- For usage via matchanalysis:
- See Open discussion in https://translate5.slack.com/archives/C046KNG7ZB8/p1670924064917259
- A TM should not be updateable (add additional TMX) if one of the assigned tasks is in status import / matchanalysis (via responseException). Also we should warn if a task is in use, but that is handled as mentioned above.
- Ensure that on getStatus call, the status in the local TM instance is update if it differs to the status returned from t5memory
- Addition: t5memory returns now additional information on the import, how many segments processed etc. This should also be reflected in the UI. Combined with the status value itself???