Translation component diagnostics

Muestra errores en la configuración de Weblate o el proyecto de traducción para cualquier componente de traducción proporcionado. Directriz sobre como encontrar dirección de incidencias también se ofrece.

Actualmente lo siguiente está cubierto:

  • Cadenas de fuente duplicadas en los archivos de traducción

  • Idiomas duplicados con las traducciones

  • Fusionar, actualizar, o subir fallos en el repositorio

  • Errores de interpretación en los archivos de traducción

  • Límites de facturación (consulte Facturación)

  • Repositorio que contiene demasiadas consignaciones salientes o al que le faltan algunas

  • Faltan licencias

  • Error al ejecutar complemento (consulte Complementos)

  • Unavailable AI evaluation services and recommendations to configure Evaluación de calidad en IA when an LLM service is available

  • Misconfigured monolingual or bilingual translation.

  • Configuración de componentes roto

  • Varias URL incorrectas

  • Capturas no utilizadas

  • Código del idioma ambiguo

  • Base nueva inutilizada dentro de los ajustes del componente

  • Máscara del archivo duplicado utilizada para los componentes enlazados

  • Conflicto al fusionar solicitud de configuración del repositorio

  • El componente parece no utilizado (configurable en UNUSED_ALERT_DAYS)

  • Unused glossary languages

  • Disabled string management in local glossaries or glossaries containing terminology

Las alertas son actualizadas diariamente, o en cambio relativo (p.ej. cuando Configuración de componentes ha cambiado o cuando el repositorio es actualizado).

Disponibilidad del sitio web de proyecto puede ser inhabilitado utilizando WEBSITE_ALERTS_ENABLED, en el cual caso Weblate no generará más alertas para sitios web del proyecto no alcanzables.

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:

Project diagnostics overview with grouped findings and filters

The workspace overview groups project-wide findings by project and identifies components using both the project and component name:

Workspace diagnostics overview with grouped findings and filters

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 componente con ambas cadenas duplicadas e idiomas como esto:

../_images/alerts.webp

Conflicto al configurar repositorio

Esta alerta se muestra cuando varios componentes de Git están configurados para enviar cambios al mismo repositorio y rama sin que todos ellos extraigan datos de esa rama. Esto incluye flujos de trabajo de solicitudes de extracción o fusión, así como envíos directos a una rama independiente. Esta configuración puede sobrescribir la rama compartida.

Para resolver esto, configure un Push branch diferente por cada componente o bien comparta el repositorio entre componentes utilizando una URL del repositorio weblate://project/component.