Developer submission context missing name field value

[wuhuang26]

Describe the issue

Mode: Weblate + Gitlab
Developer modify mid.ts file add:

<context>
    <name>AdvancedTest</name>
    <message>
        <location filename="../../src/xxxxxxxxxx" line="0"/>
        <source>Ad Test:</source>
        <translation type="unfinished"></translation>
    </message>
</context>

git push gitlab
Weblate update after translate missing name field value "AdvancedTest"

File Format: Qt Linguist translation file (*.ts)
OS: Debian11
Deployment mode: docker-compose

I already tried

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

Screenshots

How do you run Weblate?

Docker container

Weblate versions

Weblate Version: 4.13.1

Weblate deploy checks

SystemCheckError: System check identified some issues:

CRITICALS:
?: (weblate.E003) Cannot send e-mail ([Errno 99] Cannot assign requested address), please check EMAIL_* settings.
        HINT: https://docs.weblate.org/en/weblate-4.13.1/admin/install.html#out-mail
?: (weblate.E018) Failed to download avatar: HTTPSConnectionPool(host='www.gravatar.com', port=443): Max retries exceeded with url: /avatar/77a4accfa1d1d8fcae8e2f3fd42eb1de?d=identicon&s=32 (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f13db234a00>: Failed to establish a new connection: [Errno 111] Connection refused'))
        HINT: https://docs.weblate.org/en/weblate-4.13.1/admin/optionals.html#avatars

WARNINGS:
?: (security.W004) You have not set a value for the SECURE_HSTS_SECONDS setting. If your entire site is served only over SSL, you may want to consider setting a value and enabling HTTP Strict Transport Security. Be sure to read the documentation first; enabling HSTS carelessly can cause serious, irreversible problems.
?: (security.W008) Your SECURE_SSL_REDIRECT setting is not set to True. Unless your site should be available over both SSL and non-SSL connections, you may want to either set this setting True or configure a load balancer or reverse-proxy server to redirect all connections to HTTPS.
?: (security.W012) SESSION_COOKIE_SECURE is not set to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions.
?: (security.W018) You should not have DEBUG set to True in deployment.

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

System check identified 8 issues (1 silenced).
Not use email

[github-actions]

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!

[nijel]

Is the string added in Weblate, or pushed via VCS?

Is the context missing on the source string, or on the translation?

[github-actions]

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!