You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bucket remotes (sc+wal://, sc+s3://) never carry indexed transcripts or their signatures #229
BucketTransport::get_pack (crates/repo/src/bucket_transport.rs, ~494-527) builds its pack from reachability only. Unlike LocalTransport::build_pack_tempfile, it does not add the indexed transcripts (.sc/transcripts) or the signatures over them, so a fetch or clone from a bucket remote never delivers transcripts or transcript signatures.
Consequences:
A transcript attached and pushed to a bucket remote is stored there but never served back.
sc verify --require after cloning straight from a bucket has no transcript signatures to check. Snapshot signatures are affected the same way if the sender seam for them is also missing; confirm when fixing.
Expected: BucketTransport::get_pack over-sends indexed transcripts and signatures the way LocalTransport does (ADR-0038), or the bucket format records the index so the sender seam can run.
Also affects #226 (transcript drop): tombstones are Transcript objects, so bucket remotes (sc+wal/sc+s3) never serve them on fetch either. Fix together with transcripts/signatures serving.
Activity
docs,test: tighten --no-transcripts wording, name bucket remotes, add…
docs: note bucket signature/transcript gap (#229), fix CLAUDE.md depe…
tonibergholm-codento commentedon Oct 20, 2026
Also affects #226 (transcript drop): tombstones are Transcript objects, so bucket remotes (sc+wal/sc+s3) never serve them on fetch either. Fix together with transcripts/signatures serving.
feat(repo,cli): --no-transcripts for clone, fetch and push (#228)
docs: sync README, ARCHITECTURE and contributor docs with the impleme…