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

Offen
  • Stimmt etwas nicht?
#1,100 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
18/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
markdown
Bereich
documentation, localization

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TeX
Sterne
129
Forks
59
Ø Merge
2 T. 5 Std.
Gemergte PRs (30 T.)
12

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus QuantEcon/lecture-python.myst

Alle Issues in QuantEcon/lecture-python.myst

Ähnliche Issues

Weitere Issues zu Documentation

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.