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

[PATCH 1/2] t1092: add deeper changes during a checkout

From
Derrick Stolee via GitGitGadget <gitgitgadget@gmail.com>
Date
Dec 4, 2021, 02:55 UTC
Message-ID
<ba05d7d4149bc4e9e931aa225cd1fc013796d7b3.1638586534.git.gitgitgadget@gmail.com>
In-Reply-To
<pull.1092.git.1638586534.gitgitgadget@gmail.com>
From: Derrick Stolee <dstolee@microsoft.com>

Extend the repository data in the setup of t1092 to include more directories within two parent directories. This reproduces a bug found by users of the sparse index feature with suitably-complicated sparse-checkout definitions.

Add a failing test that fails in its first 'git checkout deepest' run in the sparse index case with this error:

  error: Your local changes to the following files would be overwritten by checkout:
          deep/deeper1/deepest2/a
          deep/deeper1/deepest3/a
  Please commit your changes or stash them before you switch branches.
  Aborting

The next change will fix this error, and that fix will make it clear why the extra depth is necessary for revealing this bug. The assignment of the sparse-checkout definition to include deep/deeper1/deepest as a sibling directory is important to ensure that deep/deeper1 is not a sparse directory entry, but deep/deeper1/deepest2 is.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
---
 t/t1092-sparse-checkout-compatibility.sh | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/t/t1092-sparse-checkout-compatibility.sh b/t/t1092-sparse-checkout-compatibility.sh
index 16fbd2c6db9..e6aef40e9b3 100755
--- a/t/t1092-sparse-checkout-compatibility.sh
+++ b/t/t1092-sparse-checkout-compatibility.sh
@@ -19,6 +19,8 @@ test_expect_success 'setup' '
 		mkdir folder1 folder2 deep x &&
 		mkdir deep/deeper1 deep/deeper2 deep/before deep/later &&
 		mkdir deep/deeper1/deepest &&
+		mkdir deep/deeper1/deepest2 &&
+		mkdir deep/deeper1/deepest3 &&
 		echo "after deeper1" >deep/e &&
 		echo "after deepest" >deep/deeper1/e &&
 		cp a folder1 &&
@@ -30,7 +32,9 @@ test_expect_success 'setup' '
 		cp a deep/deeper2 &&
 		cp a deep/later &&
 		cp a deep/deeper1/deepest &&
-		cp -r deep/deeper1/deepest deep/deeper2 &&
+		cp a deep/deeper1/deepest2 &&
+		cp a deep/deeper1/deepest3 &&
+		cp -r deep/deeper1/ deep/deeper2 &&
 		mkdir deep/deeper1/0 &&
 		mkdir deep/deeper1/0/0 &&
 		touch deep/deeper1/0/1 &&
@@ -126,6 +130,8 @@ test_expect_success 'setup' '
 
 		git checkout -b deepest base &&
 		echo "updated deepest" >deep/deeper1/deepest/a &&
+		echo "updated deepest2" >deep/deeper1/deepest2/a &&
+		echo "updated deepest3" >deep/deeper1/deepest3/a &&
 		git commit -a -m "update deepest" &&
 
 		git checkout -f base &&
@@ -301,6 +307,14 @@ test_expect_success 'add, commit, checkout' '
 	test_all_match git checkout -
 '
 
+test_expect_failure 'deep changes during checkout' '
+	init_repos &&
+
+	test_sparse_match git sparse-checkout set deep/deeper1/deepest &&
+	test_all_match git checkout deepest &&
+	test_all_match git checkout base
+'
+
 test_expect_success 'add outside sparse cone' '
 	init_repos &&
 
-- 
gitgitgadget
Previous: Derrick StoleeNext: Elijah Newren
Message 5 of 9 in “Sparse Index: fix a checkout bug with deep sparse-checkout patterns”
  1. 0/2 Sparse Index: fix a checkout bug with deep sparse-checkout patternsDerrick Stolee via GitGitGadget, Dec 4, 2021
  2. 2/2 unpack-trees: use traverse_path instead of nameDerrick Stolee via GitGitGadget, Dec 4, 2021
  3. Elijah NewrenDec 4, 2021
  4. Derrick StoleeDec 6, 2021
  5. 1/2 t1092: add deeper changes during a checkoutDerrick Stolee via GitGitGadget, Dec 4, 2021
  6. Elijah NewrenDec 4, 2021
  7. 0/2 Sparse Index: fix a checkout bug with deep sparse-checkout patternsDerrick Stolee via GitGitGadget, Dec 6, 2021
  8. 1/2 t1092: add deeper changes during a checkoutDerrick Stolee via GitGitGadget, Dec 6, 2021
  9. 2/2 unpack-trees: use traverse_path instead of nameDerrick Stolee via GitGitGadget, Dec 6, 2021

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.