Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The request for machine translation using Microsoft Terminology has failed [..] Failed to resolve 'api.terminology.microsoft.com' #10388

Closed
2 tasks done
dleidert opened this issue Nov 9, 2023 · 3 comments · Fixed by #10474
Assignees
Labels
bug Something is broken.
Milestone

Comments

@dleidert
Copy link

dleidert commented Nov 9, 2023

Describe the issue

I receive the following error whenever I go to the automatic suggestions tab:

The request for machine translation using Microsoft Terminology has failed: ConnectionError(MaxRetryError('HTTPSConnectionPool(host=\'api.terminology.microsoft.com\', port=443): Max retries exceeded with url: /Terminology.svc?wsdl (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x7f5ecc233c90>: Failed to resolve \'api.terminology.microsoft.com\' ([Errno -2] Name or service not known)"))'))

Indeed, that domain does not resolve (I tried from different systems located in different regions). The Microsoft Terminology service itself does still exist, though.

I already tried

  • I've read and searched the documentation.
  • I've searched for similar issues in this repository.

Steps to reproduce the behavior

Enable "Microsoft Terminology" in "Automatic Suggestions". The mentioned error appears whenever the automatic suggestions tab is active.

Expected behavior

If that service is no longer accessible, then it should probably be removed. If the API-URL has changed, then it should be updated.

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

Docker container

Weblate versions

  • Weblate: 5.1.1
  • Django: 4.2.7
  • siphashc: 2.3
  • translate-toolkit: 3.10.1
  • lxml: 4.9.3
  • Pillow: 10.1.0
  • nh3: 0.2.14
  • python-dateutil: 2.8.2
  • social-auth-core: 4.5.0
  • social-auth-app-django: 5.4.0
  • django-crispy-forms: 2.1
  • oauthlib: 3.2.2
  • django-compressor: 4.4
  • djangorestframework: 3.14.0
  • django-filter: 23.3
  • django-appconf: 1.0.5
  • user-agents: 2.2.0
  • filelock: 3.13.1
  • rapidfuzz: 3.4.0
  • openpyxl: 3.1.2
  • celery: 5.3.4
  • django-celery-beat: 2.5.0
  • kombu: 5.3.2
  • translation-finder: 2.15
  • weblate-language-data: 2023.5
  • html2text: 2020.1.16
  • pycairo: 1.25.1
  • PyGObject: 3.46.0
  • diff-match-patch: 20230430
  • requests: 2.31.0
  • django-redis: 5.4.0
  • hiredis: 2.2.3
  • sentry-sdk: 1.34.0
  • Cython: 3.0.5
  • misaka: 2.1.1
  • GitPython: 3.1.40
  • borgbackup: 1.2.6
  • pyparsing: 3.1.1
  • ahocorasick_rs: 0.20.0
  • python-redis-lock: 4.0.0
  • charset-normalizer: 3.3.2
  • Python: 3.11.5
  • Git: 2.39.2
  • psycopg2: 2.9.9
  • phply: 1.2.6
  • ruamel.yaml: 0.18.5
  • tesserocr: 2.6.2
  • boto3: 1.28.77
  • zeep: 4.2.1
  • aeidon: 1.13
  • iniparse: 0.5
  • mysqlclient: 2.2.0
  • Mercurial: 6.5.2
  • git-svn: 2.39.2
  • git-review: 2.3.1
  • PostgreSQL server: 14.9
  • Database backends: django.db.backends.postgresql
  • Cache backends: default:RedisCache, avatar:FileBasedCache
  • Email setup: django.core.mail.backends.smtp.EmailBackend: mail.wgdd.de
  • OS encoding: filesystem=utf-8, default=utf-8
  • Celery: redis://cache:6379/1, redis://cache:6379/1, regular
  • Platform: Linux 6.1.0-7-amd64 (x86_64)

Weblate deploy checks

System check identified some issues:

INFOS:
?: (weblate.I021) Error collection is not set up, it is highly recommended for production use
	HINT: https://docs.weblate.org/en/weblate-5.1.1/admin/install.html#collecting-errors

System check identified 1 issue (1 silenced).

Additional context

No response

@nijel
Copy link
Member

nijel commented Nov 9, 2023

Seems like Microsoft killed this service, see https://slator.com/microsoft-kills-off-beloved-language-portal/.

The data is now only available via web at https://msit.powerbi.com/view?r=eyJrIjoiODJmYjU4Y2YtM2M0ZC00YzYxLWE1YTktNzFjYmYxNTAxNjQ0IiwidCI6IjcyZjk4OGJmLTg2ZjEtNDFhZi05MWFiLTJkN2NkMDExZGI0NyIsImMiOjV9

Probably it's time to remove this machine translation service from Weblate...

Copy link

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

@github-actions github-actions bot added the wontfix Nobody will work on this. label Nov 24, 2023
@nijel nijel added bug Something is broken. and removed wontfix Nobody will work on this. labels Nov 24, 2023
@nijel nijel added this to the 5.3 milestone Nov 24, 2023
@nijel nijel self-assigned this Nov 24, 2023
nijel added a commit to nijel/weblate that referenced this issue Nov 24, 2023
The API is no longer provided by Microsoft, so there is no point in
keeping the integration.

Fixes WeblateOrg#10388
nijel added a commit to nijel/weblate that referenced this issue Nov 24, 2023
The API is no longer provided by Microsoft, so there is no point in
keeping the integration.

Fixes WeblateOrg#10388
nijel added a commit to nijel/weblate that referenced this issue Nov 24, 2023
The API is no longer provided by Microsoft, so there is no point in
keeping the integration.

Fixes WeblateOrg#10388
nijel added a commit that referenced this issue Nov 24, 2023
The API is no longer provided by Microsoft, so there is no point in
keeping the integration.

Fixes #10388
Copy link

Thank you for your report; the issue you have reported has just been fixed.

  • In case you see a problem with the fix, please comment on this issue.
  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants