Publish: continue on failure for the remaining writes after one item fails #4
Labels
No labels
feature request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rhelwig/DecentSite#4
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
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:
Follow-up notes: https://git.ronhelwig.com/rhelwig/DecentSite/src/branch/main/docs/PUBLISH-FOLLOWUPS-2026-10-10.md
Progress: implemented on branch
fix/auth-continue-on-fail(dafcf6c,1a918bf,45b4023), PR #8.Remaining: install 0.1.17 on a device (built on the laptop with the existing debug key) and confirm in the next real publish.
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 tomainind379421. The 0.1.17 version number from PR #8 was superseded; the changelog indocs/DECENTSITE-AUTH.mdnow 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.