inbuxa/inbuxa-migrate
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

export: a dry run that predicts failures and exits as the real run would #11

Merged
jcoffey-dev merged 2 commits from feat/predictive-dry-run into main 2026-09-30 19:49:53 +00:00
Conversation 0 Commits 2 Files Changed 8
+673 -18
2 Commits
Author SHA1 Message Date
jcoffey-dev e47c074d43 export: a dry run that predicts failures and exits as the real run would
ci / test (pull_request) Skipped
Details
github/ci (branch) GitHub Actions
Details
ci / github (pull_request) Successful in 2m30s
Details
ci / announce (pull_request) Skipped
Details 
export --dry-run counted what it would create and printed a table, but it
missed the failures it could see coming and always exited 0.

It now checks, before anything is written:
- a message larger than the target's maxSizeUpload;
- an object too large for one request under maxSizeRequest, as a contact
  with its photo inlined can be;
- a Sieve script the target would reject, with SieveScript/validate, after
  the vnd.stalwart names are renamed, so what is checked is what would be
  uploaded. Sieve scripts are uploaded as blobs for that check, and nothing
  else is; a target without the method gets one warning.

The counts are kept instead of being dropped, so a dry run in which
anything would fail exits 5, like the real run. The report is now a plan in
plain words -- per type, what would be created, updated, left unchanged,
deleted and would fail -- followed by each predicted failure and why.
 2026-09-30 12:46:38 -07:00
jcoffey-dev 1d63dfe25e export: a dry run no longer claims the default address book 
When export created a default address book, it went on to send
AddressBook/set with onSuccessSetIsDefault -- in a dry run too, naming the
dry run's made-up id. A dry run writes nothing; the claim is now only
counted as planned.
 2026-09-30 12:46:38 -07:00