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

Aperta
  • Qualcosa non va?
#1,100 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
18/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
markdown
Ambito
documentation, localization

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TeX
Stelle
129
Fork
59
Merge medio
2g 10h
PR unite (30g)
11

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di QuantEcon/lecture-python.myst

Tutte le issue di QuantEcon/lecture-python.myst

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.