Details
-
Bug
-
Resolution: Unresolved
-
None
-
None
-
Critical
-
When t5memory server config points to a non reachable URL, InstantTranslate is not working properly even if there is no TM used.
-
Empty show more show less
Description
problem
Configure t5memory server name to an existing hostname (so that no DNS exception is triggered) but the host must be down (or port closed → not tested).
Even if there is no TM uploaded / LanguageResource created, InstantTranslate is hanging in an endless loop with a loading screen. But also if a t5memory language resource does exist, should be queried but is not reachable, this should simply be shown as an error to the user and logged in the system log, but should not lead to hanging requests.
Solution
This should not be the case. In the background we should get a log that there is a service available, but InstantTranslate should not be blocked.