Operators hit one question before any migration: how big is this, and how long will it take? --estimate answers it without committing.
inbuxa-migrate import <source> … --estimate connects to the source, reports how much is new to fetch since the archive was last filled — counts, bytes and a rough time — and writes nothing (it implies --dry-run).
Estimate (no writes):
mailbox: 2 new
email: 24,318 new, 4.2 GB
----
total: 24,320 new, 4.2 GB
rough time: 20–81 min (first run, no measured rate yet)
How it works. It reuses each source's existing dry-run delta enumeration (new vs already in the archive — so a re-estimate against a filled archive correctly shows only what arrived since) and adds a size pass that asks the source only for sizes, never bodies: over IMAP a UID FETCH … RFC822.SIZE, on a Maildir the file lengths.
Scope (v1). IMAP and Maildir report sizes today — that is ~all the volume in a real mail migration. Other sources fall back to a plain dry-run with a note (--estimate isn't available for this source yet); adding each is small per-source follow-up work (Takeout needs message-level counting; CalDAV/CardDAV have getcontentlength in the PROPFIND; EWS has item sizes in enumeration). Measured-throughput time (vs the conservative default rate) is a noted follow-up too.
Design calls (agreed): a --estimate flag on import, not a standalone verb (which would duplicate the 8-source arg tree); v1 ships a clearly-labeled rough time range.
Code.TypeCounts gains a bytes field; sync::estimate renders the report; a want_sizes flag threads into the IMAP and Maildir dry-run summaries. README + unit tests (byte formatting, time range, report rendering); smoke-tested end to end against a Maildir, including the delta path. cargo test --locked (the CI gate), fmt and clippy -D warnings all pass.
Operators hit one question before any migration: how big is this, and how long will it take? `--estimate` answers it without committing.
`inbuxa-migrate import <source> … --estimate` connects to the source, reports how much is **new** to fetch since the archive was last filled — counts, bytes and a rough time — and **writes nothing** (it implies `--dry-run`).
```
Estimate (no writes):
mailbox: 2 new
email: 24,318 new, 4.2 GB
----
total: 24,320 new, 4.2 GB
rough time: 20–81 min (first run, no measured rate yet)
```
**How it works.** It reuses each source's existing dry-run delta enumeration (new vs already in the archive — so a re-estimate against a filled archive correctly shows only what arrived since) and adds a size pass that asks the source **only for sizes, never bodies**: over IMAP a `UID FETCH … RFC822.SIZE`, on a Maildir the file lengths.
**Scope (v1).** IMAP and Maildir report sizes today — that is ~all the volume in a real mail migration. Other sources fall back to a plain dry-run with a note (`--estimate isn't available for this source yet`); adding each is small per-source follow-up work (Takeout needs message-level counting; CalDAV/CardDAV have `getcontentlength` in the PROPFIND; EWS has item sizes in enumeration). Measured-throughput time (vs the conservative default rate) is a noted follow-up too.
**Design calls (agreed):** a `--estimate` flag on `import`, not a standalone verb (which would duplicate the 8-source arg tree); v1 ships a clearly-labeled *rough* time range.
**Code.** `TypeCounts` gains a `bytes` field; `sync::estimate` renders the report; a `want_sizes` flag threads into the IMAP and Maildir dry-run summaries. README + unit tests (byte formatting, time range, report rendering); smoke-tested end to end against a Maildir, including the delta path. `cargo test --locked` (the CI gate), fmt and clippy `-D warnings` all pass.
Before committing to a migration, an operator wants to know how big it
is. --estimate connects to the source, reports how much is new to fetch
since the archive was last filled -- counts, bytes and a rough time --
and writes nothing. It implies --dry-run.
It reuses each source dry run's delta enumeration (new vs already in
the archive) and adds a size pass that asks only for sizes, never bodies:
over IMAP a UID FETCH RFC822.SIZE, on a Maildir the file lengths. Those
two sources report sizes today; the others fall back to a plain dry run
with a note, which is per-source follow-up work.
TypeCounts gains a bytes field; sync::estimate renders the report, with
a wide, clearly-rough time range since a first run has no measured
throughput to go on.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Operators hit one question before any migration: how big is this, and how long will it take?
--estimateanswers it without committing.inbuxa-migrate import <source> … --estimateconnects to the source, reports how much is new to fetch since the archive was last filled — counts, bytes and a rough time — and writes nothing (it implies--dry-run).How it works. It reuses each source's existing dry-run delta enumeration (new vs already in the archive — so a re-estimate against a filled archive correctly shows only what arrived since) and adds a size pass that asks the source only for sizes, never bodies: over IMAP a
UID FETCH … RFC822.SIZE, on a Maildir the file lengths.Scope (v1). IMAP and Maildir report sizes today — that is ~all the volume in a real mail migration. Other sources fall back to a plain dry-run with a note (
--estimate isn't available for this source yet); adding each is small per-source follow-up work (Takeout needs message-level counting; CalDAV/CardDAV havegetcontentlengthin the PROPFIND; EWS has item sizes in enumeration). Measured-throughput time (vs the conservative default rate) is a noted follow-up too.Design calls (agreed): a
--estimateflag onimport, not a standalone verb (which would duplicate the 8-source arg tree); v1 ships a clearly-labeled rough time range.Code.
TypeCountsgains abytesfield;sync::estimaterenders the report; awant_sizesflag threads into the IMAP and Maildir dry-run summaries. README + unit tests (byte formatting, time range, report rendering); smoke-tested end to end against a Maildir, including the delta path.cargo test --locked(the CI gate), fmt and clippy-D warningsall pass.