Translation component diagnostics¶
Mostra erros na configuração do Weblate ou no projeto de tradução de qualquer componente de tradução. Orientação sobre como resolver os problemas encontrados também é oferecida.
Atualmente, o seguinte é coberto:
Textos fonte duplicados em arquivos de tradução
Idiomas duplicados nas traduções
Falhas de mesclagem, atualização ou envio no repositório
Erros de análise nos arquivos de tradução
Limites de cobrança (consulte Cobrança)
Repositório contendo muitos commits para serem enviados ou em falta
Licenças faltantes
Erros ao executar o complemento (consulte Complementos)
Misconfigured monolingual or bilingual translation.
Configuração de componente quebrada
URLs quebradas
Capturas de tela não usadas
Código do idioma ambíguo
Nova base não utilizada nas configurações de componente
Máscara de arquivo duplicada usada para componentes vinculados
Conflicting merge request repository setup
Component seems unused (configurable by
UNUSED_ALERT_DAYS)Unused glossary languages
Os alertas são atualizados diariamente, ou sobre mudanças relacionadas (por exemplo, quando Configuração de componente é alterada ou quando o repositório é atualizado).
Project website availability checks can be disabled using
WEBSITE_ALERTS_ENABLED, in which case Weblate will no longer
generate alerts for unreachable project websites.
Alerts are listed on each respective component page as Diagnostics.
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. Problem alerts cannot be ignored, but will disappear once the underlying problem has been fixed.
Information and warning alerts are used for guidance on improving community localization. These can be dismissed and make the Diagnostics tab visible, but they do not indicate a component problem in listings.
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.
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.
Um componente com textos e idiomas duplicados tem a seguinte aparência:
Conflicting repository setup¶
This alert is shown when multiple Git components are configured to push to the same repository and push branch without all of them pulling from that branch. This includes pull or merge request workflows, and direct pushes to a separate push branch. Such a setup can overwrite the shared branch.
To resolve this, either configure a different Push branch for each
component or share the repository between components using a
weblate://project/component repository URL.