Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-3075

Filetranslation error handling on not available language resources

    XMLWordPrintable

Details

    • Critical
    • -

    Description

      problem

      When using pre-translation, especially on using instanttranslate file translation, errors of batch pre-translations are not properly handled.

      problem 1: empty targets due single failing requests

      For example when using DeepL, and one DeepL batch request is running into a timeout, this is logged but the segments are not translated. This is OK for an ordinary task - in that case the user has to do the translation - but thats a problem for automated instanttranslate file translations. Here a single timed outed request should be just repeated. If the whole service is not reachable / down the process of automated translation should fail in a way the user gets the info what the problem is. See also TRANSLATE-2217 for the high end solution.

      problem 2: DeepL is generally not available

      DeepL is sometimes not available with strange and different "signatures". For TS-1989 it was the following error:

      Array
      (
          [service] => DeepL - https://api.deepl.com
          [languageResource] => 
          [error] => stdClass Object
              (
                  [method] => GET
                  [url] => https://api.deepl.com:443/v2/usage
                  [type] => HTTP 503
                  [body] => <!DOCTYPE html><html lang="en"><head><meta charset="utf-8"/><title>Page Load Error</title><style>
      .button{background-color:#0f2b46;border:none;color:#fff;padding:15px;text-align:center;text-decoration:none;display:inline-block;font-size:16px;margin:4px 2px;cursor:pointer;border-radius:8px;max-width:100px}div.content{margin:center;width:500px}button,h1,object,p{text-align:center;font-family:-apple-system,BlinkMacSystemFont,Segoe UI,Roboto,Helvetica,Arial,sans-serif!important}.centering{display:flex;justify-content:center;align-items: center;flex-direction: column}#robot{max-width:200px}#reload-button{padding:2em}
      </style><link rel="icon" type="image/png" href="https://static.deepl.com/img/favicon/favicon_16.png" sizes="16x16" /><link rel="icon" type="image/png" href="https://static.deepl.com/img/favicon/favicon_32.png" sizes="32x32" /><link rel="icon" type="image/png" href="https://static.deepl.com/img/favicon/favicon_96.png" sizes="96x96" /></head>
      <body><main><div class=centering><img width="100px" src="https://static.deepl.com/img/logo/DeepL_Logo_darkBlue_v2.svg" />
      
      <h1>We're sorry!</h1>
      <div class=centering><img id="robot" src="https://static.deepl.com/img/404/robot.svg"/></div>
      <p>Something went wrong. We're working on it </p>
      <p>Try reloading this page or come back later.</p>
      <div class=centering id=reload-button><button onClick="location.reload();" class="button">Reload</button></div>
      </main></body></html>
      
      
      
                  [error] => 503
              )
      
      ) 

      This was logged in another instance at the same time as the pre-translation was not working in TS-1989, but in the mentioned issue there was no error message at all. The setup here was using a TM translating some of the segments, and the rest should have been translated by DeepL - which was just not done, assuming due the above error.

      In such a scenario the whole file translation should fail with an appropriate error message to the user in instanttranslate.

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              tlauria Thomas Lauria
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: