Document bootstrap batch resume

d426f33→main·

Soph·3mo ago·3 files·+5 added/-3 removed

Sessions

ffd71d2ccb2aView transcript

Can you take a look at the go code (wasm) in /Users/soph/Work/entire/devenv/entire-io-worktree1 based a bit on that I wonder if something like this can be build:Codex·GPT-5.4·1 step

Changes

3

• MREADME.md+2/-2
• docs
• • Mbootstrap-batching.md+1
• • Mbootstrap.md+2/-1

90 unmodified lines
91
92
93
94
94
95
96
97
98
71 unmodified lines

170
171
172
173
173
174
175
176

90 unmodified lines

- protocol v2 only
- branch refs only
- no tags
- no resume
- temporary refs under `refs/gitsync/bootstrap/heads/`
- resume from existing temp refs is supported when they match a planned checkpoint

Add `--measure-memory` to `bootstrap`, `sync`, `plan`, `probe`, or `fetch` to sample elapsed time and Go heap usage:

71 unmodified lines

- `probe` returns top-level keys such as `source_url`, `target_url`, `protocol`, `ref_prefixes`, `source_capabilities`, `target_capabilities`, `refs`, and `stats`
- `fetch` returns top-level keys such as `source_url`, `protocol`, `wants`, `haves`, `fetched_objects`, and `stats`
- `bootstrap`, `plan`, and `sync` return top-level keys such as `plans`, `pushed`, `skipped`, `blocked`, `deleted`, `dry_run`, `protocol`, and `stats`
- `bootstrap`, `plan`, and `sync` also expose `relay`, `relay_mode`, `relay_reason`, `batching`, and `batch_count`
- `bootstrap`, `plan`, and `sync` also expose `relay`, `relay_mode`, `relay_reason`, `batching`, `batch_count`, `planned_batch_count`, and `temp_refs`
- each item in `plans` includes stable string fields such as `branch`, `source_ref`, `target_ref`, `source_hash`, `target_hash`, `kind`, `action`, and `reason`

Probe both source and target remotes to inspect source fetch capabilities and target `receive-pack` capabilities:

MREADME.md+2/-2

251 unmodified lines
252
253
254
255
256
257
258

251 unmodified lines

- implemented via `git-sync bootstrap --batch-max-pack-bytes`
- currently requires source-side protocol v2 with fetch filter support
- resumes from an existing temp ref when that temp ref matches a planned checkpoint
- exercised by `TestBootstrap_GitHTTPBackendBatchedBranch`

Phase B:

Mdocs/bootstrap-batching.md+1

169 unmodified lines
170
171
172
173
173
174
175
176
177

169 unmodified lines

- the current batched bootstrap path is intentionally narrow
- it requires source-side protocol v2 with fetch filters
- it supports branch refs only
- it does not support tags or resume yet
- it does not support tags yet
- it resumes from an existing temp ref when that temp ref matches a planned checkpoint
- it uses temporary target refs under `refs/gitsync/bootstrap/heads/`

Phase 4:

Mdocs/bootstrap.md+2/-1