git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [BUG] git bundle create with bitmaps omits tree required by advertised ref

From
Taylor Blau <ttaylorr@openai.com>
Date
Sep 8, 2026, 22:33 UTC
Message-ID
<aqCNL8y9wLLP4ovm@com-79390>
In-Reply-To
<CALY5j-0K-LfowAavH8X3UfZ24eAsoX=xew=KTt=4uCfZrdwXQw@mail.gmail.com>
On Tue, Sep 08, 2026 at 10:23:37AM +0200, Peter Elmers wrote:
Show 10 quoted lines
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> I created two sibling commits with the same root tree, stored one at a local
> branch and the other at a remote-tracking ref, wrote a pack bitmap, and created
> a bundle that included the local branch while excluding the remote-tracking
> ref.
>
> Adding `-c pack.useBitmaps=false` appears to fix the issue.
>
> The following script reproduces the issue:

Interesting. I reproduced what you wrote here using your script. I highly suspect what's going on here is that the non-bitmap case overcounts some objects beyond the boundary whereas the bitmap case builds an exact answer.

The non-bitmap traversal only marked boundary trees UNINTERESTING in this case, so it happened to keep the shared tree.

We can fix this with something like the following (only lightly tested) patch, but it has some test fallout for cases where we generate bundles with only tags (+CC Peff who may have some opinions).

--- 8< ---
Subject: [PATCH] bundle: restrict pack haves to recorded prerequisites
`write_pack_data()` uses every UNINTERESTING tip as a pack have, but the
bundle header records only boundary commits. If an included commit
shares a tree with an excluded sibling, a bitmap walk can omit that tree
while the header requires only their parent. A recipient with the parent
  can verify and unbundle the result while lacking the advertised
  commit's tree.

Restrict pack haves to UNINTERESTING commits marked BOUNDARY, which are recorded as prerequisites. Other excluded tips must not suppress objects that the advertised refs need.

As a consequence, there is a bit of test fallout in t6020.13. That test includes the tags while excluding all branch tips. Its header records no prerequisites, but its pack previously contained only the three tag objects: the excluded tips caused their target histories to be omitted.

But that bundle was already incomplete! With no prerequisites, it must provide the history reachable from its advertised tags. Restricting pack haves to recorded prerequisites includes that history, increasing the expected object count as below.

Reported-by: Peter Elmers <peter.elmers@databricks.com>
Signed-off-by: Taylor Blau <ttaylorr@openai.com>
---
 bundle.c               |  7 +++++--
 t/t6020-bundle-misc.sh | 14 ++++++++++++--
 2 files changed, 17 insertions(+), 4 deletions(-)
diff --git a/bundle.c b/bundle.c
index f55a521b2a1..06a52b8e705 100644
--- a/bundle.c
+++ b/bundle.c
@@ -359,10 +359,13 @@ static int write_pack_data(int bundle_fd, struct rev_info *revs, int progress)

 	for (i = 0; i < revs->pending.nr; i++) {
 		struct object *object = revs->pending.objects[i].item;
-		if (object->flags & UNINTERESTING)
+		if (object->flags & UNINTERESTING) {
+			if (!(object->flags & BOUNDARY))
+				continue; /* Not a bundle prerequisite. */
 			oid_array_append(&opts.haves, &object->oid);
-		else
+		} else {
 			oid_array_append(&opts.wants, &object->oid);
+		}
 	}

 	if (odb_generate_pack(revs->repo->objects, &generator, &opts)) {
diff --git a/t/t6020-bundle-misc.sh b/t/t6020-bundle-misc.sh
index 939d4214f4d..6fce6252a11 100755
--- a/t/t6020-bundle-misc.sh
+++ b/t/t6020-bundle-misc.sh
@@ -446,8 +446,9 @@ test_expect_success 'create bundle 4 - with tags' '
 		make_user_friendly_and_stable_output >actual &&
 	test_cmp expect actual &&

-	test_bundle_object_count       4.bdl 3 &&
-	test_bundle_object_count stdin-4.bdl 3
+	# With no prerequisites, include the tag targets and their history.
+	test_bundle_object_count       4.bdl 40 &&
+	test_bundle_object_count stdin-4.bdl 40
 '

 test_expect_success 'clone from bundle' '
@@ -784,4 +785,13 @@ do
 	'
 done

+test_expect_success 'bundle with bitmaps includes trees shared with an excluded sibling' '
+	commit=$(git commit-tree main^{tree} -p main^ -m rewritten) &&
+	git branch rewritten "$commit" &&
+	test_when_finished "git branch -D rewritten" &&
+	git repack -adb &&
+	git -c pack.useBitmaps=true bundle create bitmap.bdl main..rewritten &&
+	test_bundle_object_count bitmap.bdl 3
+'
+
 test_done

base-commit: b8242b093d9e941a34460d715e3ce616a34ac3fe
--
2.55.0.openai.744.g47c847ce2641
Previous: Peter Elmers
Message 2 of 2 in “[BUG] git bundle create with bitmaps omits tree required by advertised ref”
  1. Peter ElmersSep 8, 2026
  2. Taylor BlauSep 8, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.