Bad statistics reported for categories

[surli]

Describe the issue

In our own instance of Weblate recently upgraded to 5.9.2 we're seeing that some categories are not marked as 100% translated in German, while when entering into the category all components are actually 100% translated. And using the link to access untranslated words displays a warning "No string found!".

I already tried

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

Steps to reproduce the behavior

1. Go to https://l10n.xwiki.org/projects/xwiki-platform/-/de/
2. See that xwiki-platform-extension and xwiki-platform-help are apparently not entirely translated
3. Click on the link for unfinished translation, check that it shows "No strings found! "
4. Go inside one of the category and see that everything's already translated.

Expected behavior

The categories should be marked as entirely translated.

Screenshots

Exception traceback

No response

How do you run Weblate?

PyPI module

Weblate versions

Weblate: 5.9.2
Django: 5.1.4
siphashc: 2.3
translate-toolkit: 3.14.5
lxml: 5.3.0
pillow: 11.1.0
nh3: 0.2.15
python-dateutil: 2.8.2
social-auth-core: 4.5.1
social-auth-app-django: 5.4.2
django-crispy-forms: 2.3
oauthlib: 3.2.2
django-compressor: 4.4
djangorestframework: 3.15.2
django-filter: 24.3
django-appconf: 1.0.6
user-agents: 2.2.0
filelock: 3.16.1
RapidFuzz: 3.11.0
openpyxl: 3.1.2
celery: 5.4.0
django-celery-beat: 2.7.0
kombu: 5.3.4
translation-finder: 2.19
weblate-language-data: 2024.16
html2text: 2024.2.26
pycairo: 1.25.1
PyGObject: 3.46.0
diff-match-patch: 20241021
requests: 2.32.3
django-redis: 5.4.0
hiredis: 2.2.3
sentry-sdk: 2.19.2
Cython: 3.0.11
mistletoe: 1.4.0
GitPython: 3.1.40
borgbackup: 1.2.7
pyparsing: 3.1.1
ahocorasick_rs: 0.22.1
python-redis-lock: 4.0.0
charset-normalizer: 3.3.2
cyrtranslit: 1.1.1
drf-spectacular: 0.28.0
Python: 3.11.2
Git: 2.39.5
psycopg: 3.1.17
psycopg-binary: 3.1.17
phply: 1.2.6
ruamel.yaml: 0.17.40
tesserocr: 2.6.2
boto3: 1.28.85
aeidon: 1.15
iniparse: 0.5
google-cloud-translate: 3.19.0
openai: 1.59.7
Mercurial: 6.9
git-review: 2.4.0
PostgreSQL server: 15.10
Database backends: django.db.backends.postgresql
PostgreSQL implementation: psycopg3 (binary)
Cache backends: default:RedisCache, avatar:FileBasedCache
Email setup: django.core.mail.backends.smtp.EmailBackend: localhost
OS encoding: filesystem=utf-8, default=utf-8
Celery: redis://localhost:6379, redis://localhost:6379, regular
Platform: Linux 6.1.0-17-amd64 (x86_64)

Weblate deploy checks

No response

Additional context

No response

[nijel]

Were the stats correct before the upgrade? I recall we fixed something like this in past. So it might get fixed once they are recalculated.

[surli]

Were the stats correct before the upgrade?

Checking with the reporter I'll keep you in touch.

So it might get fixed once they are recalculated.

Is there a way to force a recomputation?

[surli]

Were the stats correct before the upgrade?

So apparently yes they were, see: https://forum.xwiki.org/t/planned-upgrade-of-weblate-in-l10n-xwiki-org/16232/7

[nijel]

The upgrade itself doesn't recalculate the statistics, these are only updated upon some change. Anyway when I look there now, it all looks correct...

[surli]

Anyway when I look there now, it all looks correct...

Indeed... weird. I created new components today maybe there was some recomputation?