Translation sync failed for PR #1099 (zh-cn)

Abierto
  • ¿Algo no está bien?
#1,100 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
markdown
Área
documentation, localization

Línea de trabajo

The failures are in lectures/likelihood_ratio_process_2.md and lectures/mix_model.md, which the sync tool translated into the zh-cn repo for PR #1099. Start by comparing the directive sequence of the source and the output of mix_model.md, since the output has three extra directives and shifted names from line 783 onward. Done means the sync completes without parity errors and the \translate-resync comment on PR #1099 succeeds. This needs knowledge of the translation pipeline, so ask maintainers before starting.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

translation-sync-failure
Translation sync failure

Source PR: #1099
Target repo: QuantEcon/lecture-python.zh-cn
Target language: zh-cn

Errors
  • Error processing lectures/likelihood_ratio_process_2.md: Error: Translation failed for modified section: translateSectionUpdate: Response truncated at max_tokens=16384; refusing to interpret incomplete output
  • Error processing lectures/mix_model.md: Error: structural parity check failed for lectures/mix_model.md:
    • directive count differs: source has 38, output has 41 — a wholesale mismatch usually means the document was re-fenced or truncated
    • directive #17 name changed: source line 783 has {exercise}, output line 587 has {code-cell}
    • directive #18 name changed: source line 814 has {solution-start}, output line 675 has {code-cell}
    • directive #20 name changed: source line 863 has {code-cell}, output line 793 has {exercise}
    • directive #21 name changed: source line 887 has {code-cell}, output line 823 has {solution-start}
    • directive #24 name changed: source line 964 has {solution-end}, output line 896 has {code-cell}
    • directive #25 name changed: source line 967 has {exercise}, output line 912 has {code-cell}
    • directive #26 name changed: source line 979 has {solution-start}, output line 944 has {code-cell}
    • directive #27 name changed: source line 985 has {code-cell}, output line 973 has {solution-end}
    • directive #28 name changed: source line 998 has {code-cell}, output line 976 has {exercise}
    • directive #29 name changed: source line 1028 has {solution-end}, output line 988 has {solution-start}
    • directive #30 name changed: source line 1031 has {exercise}, output line 994 has {code-cell}
    • directive #31 name changed: source line 1047 has {solution-start}, output line 1007 has {code-cell}
    • directive #32 name changed: source line 1061 has {code-cell}, output line 1037 has {solution-end}
    • directive #33 name changed: source line 1079 has {solution-end}, output line 1040 has {exercise}
    • directive #34 name changed: source line 1082 has {exercise}, output line 1056 has {solution-start}
    • directive #35 name changed: source line 1096 has {solution-start}, output line 1070 has {code-cell}
    • directive #36 name changed: source line 1100 has {code-cell}, output line 1088 has {solution-end}
    • directive #37 name changed: source line 1116 has {code-cell}, output line 1091 has {exercise}
    • directive #38 name changed: source line 1146 has {solution-end}, output line 1105 has {solution-start}
Recovery

Once the issue is resolved, comment \translate-resync on PR #1099 to retry.

Lenguaje dominante
TeX
Estrellas
129
Forks
59
Merge medio
2 d 10 h
PR fusionados (30 d)
11

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de QuantEcon/lecture-python.myst

Todos los issues de QuantEcon/lecture-python.myst

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.