Skip to content

fix: a sync that fails exits non-zero, and an oversized body is refused locally (#130) - #241

Open
androidand wants to merge 1 commit into
mainfrom
fix/130-sync-fails-loudly
Open

androidand wants to merge 1 commit into
mainfrom
fix/130-sync-fails-loudly

Conversation

@androidand

Copy link
Copy Markdown
Owner
  • A change that fails to sync no longer vanishes: the run exits 1, the summary reads N created, N updated, K failed, and the failed changes are listed at the end.
  • A body over GitHub's 65,536-character limit is refused before any network call, naming the change, the length, the largest part and the remedy. It applies under -dry-run too.
  • Records the failed/skipped/no-op taxonomy in design.md.
  • Still open on A sync that fails must fail loudly #130: -dry-run printing every change's body size, and a skipped no-proposal change being reported.

Refs #130

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying specsync with  Cloudflare Pages  Cloudflare Pages

Latest commit: c8589c3
Status: ✅  Deploy successful!
Preview URL: https://ac8a4827.specsync.pages.dev
Branch Preview URL: https://fix-130-sync-fails-loudly.specsync.pages.dev

View logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant