Publish: continue on failure for the remaining writes after one item fails #4

Closed
opened 2026-10-10 18:23:08 +00:00 by rhelwig · 2 comments
Owner

Today one failed step stops the whole publication run, even when the remaining writes don't depend on it.

Seen on 2026-10-10: the release had 20 writes. Auth stopped at step 2 ("Ron's Manly Buns", step: checking, OPERATION_FAILED) three times in a row because of a transient mainnet read error. Nothing was wrong with that page. Each retry had to restart the sequence at the failing item.

Wanted:

  • When one item fails, keep going with the independent remaining writes.
  • Record which items failed.
  • Let a retry or "Renew QR for remaining work" handle only what's left.
  • Keep ordering constraints. For example, the release record and site activation must come last, and only after every dependency is confirmed.
  • Show a clear summary: N confirmed, M failed (with reasons), K skipped (dependencies).

Follow-up notes: https://git.ronhelwig.com/rhelwig/DecentSite/src/branch/main/docs/PUBLISH-FOLLOWUPS-2026-10-10.md

Today one failed step stops the whole publication run, even when the remaining writes don't depend on it. **Seen on 2026-10-10:** the release had 20 writes. Auth stopped at step 2 ("Ron's Manly Buns", step: checking, OPERATION_FAILED) three times in a row because of a transient mainnet read error. Nothing was wrong with that page. Each retry had to restart the sequence at the failing item. **Wanted:** - When one item fails, keep going with the independent remaining writes. - Record which items failed. - Let a retry or "Renew QR for remaining work" handle only what's left. - Keep ordering constraints. For example, the release record and site activation must come last, and only after every dependency is confirmed. - Show a clear summary: N confirmed, M failed (with reasons), K skipped (dependencies). Follow-up notes: https://git.ronhelwig.com/rhelwig/DecentSite/src/branch/main/docs/PUBLISH-FOLLOWUPS-2026-10-10.md
Author
Owner

Progress: implemented on branch fix/auth-continue-on-fail (dafcf6c, 1a918bf, 45b4023), PR #8.

  • An item that fails on its own is recorded and the remaining writes continue. That covers reads still failing after the 0.1.16 retries, a changed operation, signing failing before the receipt, and a proven network rejection. Site activation is skipped while anything is missing.
  • Uncertain writes still stop the run and are never rebroadcast. Expiry and contract/key/nonce/protocol/credit/site changes still stop it too. It also stops after 3 failures in a row or 2 rejections in one run.
  • Auth 0.1.17 shows which steps confirmed and which failed. Check again retries only the steps still missing on Platform, with a new fee review and approval.
  • Tests use failure injection. The full TS suite passes (165/165), and the Kotlin protocol tests and app compile pass.

Remaining: install 0.1.17 on a device (built on the laptop with the existing debug key) and confirm in the next real publish.

Progress: implemented on branch `fix/auth-continue-on-fail` (`dafcf6c`, `1a918bf`, `45b4023`), PR #8. - An item that fails on its own is recorded and the remaining writes continue. That covers reads still failing after the 0.1.16 retries, a changed operation, signing failing before the receipt, and a proven network rejection. Site activation is skipped while anything is missing. - Uncertain writes still stop the run and are never rebroadcast. Expiry and contract/key/nonce/protocol/credit/site changes still stop it too. It also stops after 3 failures in a row or 2 rejections in one run. - Auth 0.1.17 shows which steps confirmed and which failed. **Check again** retries only the steps still missing on Platform, with a new fee review and approval. - Tests use failure injection. The full TS suite passes (165/165), and the Kotlin protocol tests and app compile pass. Remaining: install 0.1.17 on a device (built on the laptop with the existing debug key) and confirm in the next real publish.
Author
Owner

Follow-up: continue-on-fail (PR #8, b02f50f) is released as Auth 0.1.18 (versionCode 19), together with identity-on-any-device verification (#3), merged to main in d379421. The 0.1.17 version number from PR #8 was superseded; the changelog in docs/DECENTSITE-AUTH.md now describes both under 0.1.18.

Laptop-signed mainnet debug APK: ~/Projects/DecentSite-auth-credits/apk/decentsite-auth-0.1.18-mainnet-debug.apk. 166/166 Node tests and Kotlin protocol tests pass.

Follow-up: continue-on-fail (PR #8, b02f50f) is released as **Auth 0.1.18** (versionCode 19), together with identity-on-any-device verification (#3), merged to `main` in d379421. The 0.1.17 version number from PR #8 was superseded; the changelog in `docs/DECENTSITE-AUTH.md` now describes both under 0.1.18. Laptop-signed mainnet debug APK: `~/Projects/DecentSite-auth-credits/apk/decentsite-auth-0.1.18-mainnet-debug.apk`. 166/166 Node tests and Kotlin protocol tests pass.
Sign in to join this conversation.
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rhelwig/DecentSite#4
No description provided.