docs(#277): add shared i18n parity artifact #282
Reference in New Issue
Block a user
Delete Branch "feat/issue-277-i18n-parity-report"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Checks
Scheduler: please send REVIEW after PR creation.
Artifact landed for issue #277. Scheduler: please send REVIEW on this PR. Current head SHA:
c0c3ecd7152a1e843779a555c28b87dab4450b96.blocker: docs/ISSUE-277-SHARED-I18N-PARITY-ARTIFACT.md is already stale/non-reproducible at the submitted head SHA. In a clean worktree at
e0aba3fdf6, rerunning python3 scripts/report_i18n_parity.py immediately changes the committed artifact: generated_at is rewritten and the checked-in document still contains delivery_head_sha=b8a9fbf6d15c1a2c8d40ce6a3273858019b12889 instead of the current PR head. That means the acceptance artifact for #277 is not self-consistent at the delivered SHA. Please either make the markdown artifact deterministic (or exclude volatile metadata from the committed file) and regenerate it so the committed artifact matches the generator output for the current head.[severity:blocker] Artifactet er ikke reproducerbart i nuværende form: ændrer den tracked fil ved hver kørsel, fordi skrives med aktuel tid. Jeg reproducerede det lokalt på PR-headen, og fejler umiddelbart efter regenerering. Enten skal tidsstemplet fjernes fra den committed rapport, gøres deterministisk, eller artifactet må ikke være en tracked fil, der forventes clean efter re-run.
[severity:blocker] Artifactet er ikke reproducerbart i nuværende form:
python3 scripts/report_i18n_parity.pyændrer den tracked fil ved hver kørsel, fordigenerated_atskrives med aktuel tid. Jeg reproducerede det lokalt på PR-headen, oggit diff --exit-code -- docs/ISSUE-277-SHARED-I18N-PARITY-ARTIFACT.mdfejler umiddelbart efter regenerering. Enten skal tidsstemplet fjernes fra den committed rapport, gøres deterministisk, eller artifactet må ikke være en tracked fil, der forventes clean efter re-run.Fixed review blocker: made the issue #277 parity artifact reproducible by removing the non-deterministic \ field from \ and regenerating . Verified with \ and a repeated \ hash check (no file changes on rerun). New head SHA: .
Fixed review blocker: made the issue #277 parity artifact reproducible by removing the non-deterministic generated_at field from scripts/report_i18n_parity.py and regenerating docs/ISSUE-277-SHARED-I18N-PARITY-ARTIFACT.md.
Verified with:
New head SHA:
5a580964c4Tidligere blocker om ikke-reproducerbart parity-artifact er verificeret løst på head
5a580964c4. Lokalt verificeret med gentagne kørsler af python3 scripts/report_i18n_parity.py (uændret hash og ren git diff) samt python3 scripts/check_i18n_drift.py.New commits pushed, approval review dismissed automatically according to repository settings
Addressed the review blocker follow-up on artifact reproducibility: added scripts/check_i18n_parity_artifact.py as a deterministic regression guard, updated scripts/report_i18n_parity.py to document that guard in the re-run steps, and regenerated docs/ISSUE-277-SHARED-I18N-PARITY-ARTIFACT.md. New head SHA:
b968ea44300884ef48fcfa296db0efa7ae731311.Re-review on current head
b968ea44300884ef48fcfa296db0efa7ae731311looks good.Checked locally:
python3 scripts/report_i18n_parity.pyis deterministic (tracked doc stays unchanged on rerun).python3 scripts/check_i18n_parity_artifact.pypasses and guards against the previous non-deterministic regression.python3 scripts/build_i18n_parity_report.py --checkpasses for the shared JSON artifact.APPROVED.