Translation component diagnostics¶
Mostra errors a la configuració del Weblate o al projecte de traducció per a qualsevol component de traducció determinat. També s’ofereix orientació sobre com abordar els problemes trobats.
Actualment es cobreix el següent:
Cadenas font duplicades en fitxers de traducció
Idiomes duplicats dins de les traduccions
Merge, update, or push failures in the repository
Anàlisi d’errors als fitxers de traducció
Billing limits (see Facturació)
Repository containing too many outgoing or missing commits
Missing licenses
Errors en executar el complement (vegeu Complements)
Unavailable AI evaluation services and recommendations to configure AI quality evaluation when an LLM service is available
Misconfigured monolingual or bilingual translation.
Broken Configuració dels components
Broken URLs
Unused screenshots
Ambiguous language code
Base nova no utilitzada a la configuració dels components
Duplicate file mask used for linked components
Configuració del dipòsit de sol·licituds de combinació en conflicte
Sembla que el component no s’utilitza (configurable per
UNUSED_ALERT_DAYS)Unused glossary languages
Disabled string management in local glossaries or glossaries containing terminology
Les alertes s’actualitzen diàriament o en canvis relacionats (per exemple, quan es canvia Configuració dels components o quan s’actualitza el repositori).
Les comprovacions de disponibilitat del lloc web del projecte es poden desactivar mitjançant WEBSITE_ALERTS_ENABLED, en aquest cas Weblate ja no generarà alertes per als llocs web del projecte inaccessibles.
Alerts are listed on each respective component page as Diagnostics.
Add-on error diagnostics link to the responsible installation’s Configuration page for users who can manage it, including add-ons inherited from a category, project, or site configuration. For AI quality evaluation, an unavailable service produces an error diagnostic; provider request failures remain in the add-on activity log.
Project and workspace diagnostics overviews¶
Signed-in users can open the Diagnostics tab on project and workspace pages. The overview is loaded when opened and groups alerts of the same type instead of repeating them for every component.
The project overview shows project-wide findings once and lists the components affected by component-specific findings:
The workspace overview groups project-wide findings by project and identifies components using both the project and component name:
Each finding lists up to 20 affected projects or components. Additional affected objects are shown as a count. Follow a component link to see the complete diagnostic details or dismiss a diagnostic on the component page.
The summary can be filtered by active or dismissed state, severity, category, or whether the signed-in user can act on the diagnostic. Components shared into a project are listed only in the diagnostics of their owning project.
If it is missing, the component clears all current checks. Alerts disappear once the underlying condition has been resolved.
Information and warning alerts are used for guidance on improving community localization. They make the Diagnostics tab visible, but they do not indicate a component problem in listings.
Dismissal is available for selected diagnostics, regardless of severity. Maintainers can dismiss warnings about unused components and glossary languages when these are intentionally retained. Suspected monolingual or bilingual file-format misconfiguration can also be dismissed when the configuration is correct. Operational failures and required configuration must still be resolved.
Dismissed diagnostics record who dismissed them, when they were dismissed, and an optional reason. A dismissal is automatically reopened when the diagnostic details or the configuration relevant to that diagnostic changes. Dismissal and reopening are both recorded in the component change history.
Unused-component dismissals persist through daily checks and reopen if
UNUSED_ALERT_DAYS changes. Set this setting to 0 to disable the check
site-wide. If activity resolves the diagnostic, a later period of inactivity
can generate a new diagnostic. Unused glossary language dismissals reopen when
the affected languages change. File-format diagnostic dismissals reopen when
the relevant format, format parameters, base file, or source language changes.
Warning and error notifications are sent only to subscribed project maintainers who have permission to act on the diagnostic. Informational recommendations do not send unsolicited notifications.
Custom alerts can override
BaseAlert.get_dismissal_context(component, details) to include stable,
JSON-serializable configuration or diagnostic inputs. Changing the returned
context reopens a dismissed alert. Incidental values such as evaluation time
should not be included.
Un component amb cadenes duplicades i idiomes té aquest aspecte:
Conflicting repository setup¶
Aquesta alerta es mostra quan es configuren diversos components de Git per enviar-los al mateix repositori i enviar-los a la branca sense que tots ells treguin d’aquesta branca. Això inclou fluxos de treball de sol·licituds d’extracció o fusió i pushs directes a una branca push independent. Aquesta configuració pot sobreescriure la branca compartida.
Per resoldre-ho, configureu una Push branch diferent per a cada component o compartiu el dipòsit entre components mitjançant un URL de repositori weblate://project/component.