lunny/git-lfs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
74c51fa885
git-lfs/t/t-alternates.sh

156 lines
4.4 KiB
Bash
Raw Normal View History

fs: support multiple object alternates Like in upstream Git, Git LFS supports "object database alternates" (described in [1]) to link several object databases together. We have supported this feature since [2] but read the entire .git/objects/info/alternates in one single buffer via ioutil.ReadFile and checked if a directory existed at that location. If a user specified multiple alternates, then this will fail. Git LFS will look for a directory that has newlines in it, when what it should be doing is splitting that list by the '\n' character and checking each directory if it exists. Let's do that, and also return a []string, instead of a single string, to indicate that there might be multiple alternates in a repository. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates [2]: https://github.com/git-lfs/git-lfs/pull/1007/files
2018-07-09 15:28:23 +00:00
#!/usr/bin/env bash
t: ensure alternates test runs automatically The test for alternates was named test-alternates.sh, but only tests matching "t-*.sh" are run automatically. Since we want to make sure that alternates continue to work, rename this file. Update the source command to use the correct directory as well.
2019-08-08 14:50:39 +00:00
. "$(dirname "$0")/testlib.sh"
fs: support multiple object alternates Like in upstream Git, Git LFS supports "object database alternates" (described in [1]) to link several object databases together. We have supported this feature since [2] but read the entire .git/objects/info/alternates in one single buffer via ioutil.ReadFile and checked if a directory existed at that location. If a user specified multiple alternates, then this will fail. Git LFS will look for a directory that has newlines in it, when what it should be doing is splitting that list by the '\n' character and checking each directory if it exists. Let's do that, and also return a []string, instead of a single string, to indicate that there might be multiple alternates in a repository. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates [2]: https://github.com/git-lfs/git-lfs/pull/1007/files
2018-07-09 15:28:23 +00:00
begin_test "alternates (single)"
(
set -e
reponame="alternates-single-alternate"
setup_remote_repo_with_file "$reponame" "a.txt"
pushd "$TRASHDIR" > /dev/null
clone_repo "$reponame" "${reponame}_alternate"
popd > /dev/null
rm -rf .git/lfs/objects
alternate="$TRASHDIR/${reponame}_alternate/.git/objects"
t: make alternates test work on Windows This test works fine on Unix systems, but fails on Windows. This occurs because the MSYS environment uses Unix-style paths, but Git wants Windows-style paths in its environment and alternates files. Convert the paths to an appropriate format to ensure this test passes on Windows as well.
2019-08-14 13:49:43 +00:00
echo "$(native_path "$alternate")" > .git/objects/info/alternates
fs: support multiple object alternates Like in upstream Git, Git LFS supports "object database alternates" (described in [1]) to link several object databases together. We have supported this feature since [2] but read the entire .git/objects/info/alternates in one single buffer via ioutil.ReadFile and checked if a directory existed at that location. If a user specified multiple alternates, then this will fail. Git LFS will look for a directory that has newlines in it, when what it should be doing is splitting that list by the '\n' character and checking each directory if it exists. Let's do that, and also return a []string, instead of a single string, to indicate that there might be multiple alternates in a repository. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates [2]: https://github.com/git-lfs/git-lfs/pull/1007/files
2018-07-09 15:28:23 +00:00
Rename default branch in tests to "main" Currently, our default branch in tests is "master". This is the Git default, but the Git default will likely change in the future, so it makes sense to update our testsuite to be explicit about the branch name. We'll ensure this continues by building against older versions of Git as well as newer versions. We use "main" for the new branch name, since that's the proposed value upstream. This commit was made entirely by automated means using the following command: git grep -l master t | xargs sed -i -e 's/master/main/g'
2020-06-29 16:18:57 +00:00
GIT_TRACE=1 git lfs fetch origin main 2>&1 | tee fetch.log
fs: support multiple object alternates Like in upstream Git, Git LFS supports "object database alternates" (described in [1]) to link several object databases together. We have supported this feature since [2] but read the entire .git/objects/info/alternates in one single buffer via ioutil.ReadFile and checked if a directory existed at that location. If a user specified multiple alternates, then this will fail. Git LFS will look for a directory that has newlines in it, when what it should be doing is splitting that list by the '\n' character and checking each directory if it exists. Let's do that, and also return a []string, instead of a single string, to indicate that there might be multiple alternates in a repository. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates [2]: https://github.com/git-lfs/git-lfs/pull/1007/files
2018-07-09 15:28:23 +00:00
[ "0" -eq "$(grep -c "sending batch of size 1" fetch.log)" ]
)
end_test
begin_test "alternates (multiple)"
(
set -e
reponame="alternates-multiple-alternates"
setup_remote_repo_with_file "$reponame" "a.txt"
pushd "$TRASHDIR" > /dev/null
clone_repo "$reponame" "${reponame}_alternate_stale"
rm -rf .git/lfs/objects
popd > /dev/null
pushd "$TRASHDIR" > /dev/null
clone_repo "$reponame" "${reponame}_alternate"
popd > /dev/null
rm -rf .git/lfs/objects
alternate_stale="$TRASHDIR/${reponame}_alternate_stale/.git/objects"
alternate="$TRASHDIR/${reponame}_alternate/.git/objects"
t: make alternates test work on Windows This test works fine on Unix systems, but fails on Windows. This occurs because the MSYS environment uses Unix-style paths, but Git wants Windows-style paths in its environment and alternates files. Convert the paths to an appropriate format to ensure this test passes on Windows as well.
2019-08-14 13:49:43 +00:00
echo "$(native_path "$alternate")" > .git/objects/info/alternates
echo "$(native_path "$alternate_stale")" >> .git/objects/info/alternates
fs: support multiple object alternates Like in upstream Git, Git LFS supports "object database alternates" (described in [1]) to link several object databases together. We have supported this feature since [2] but read the entire .git/objects/info/alternates in one single buffer via ioutil.ReadFile and checked if a directory existed at that location. If a user specified multiple alternates, then this will fail. Git LFS will look for a directory that has newlines in it, when what it should be doing is splitting that list by the '\n' character and checking each directory if it exists. Let's do that, and also return a []string, instead of a single string, to indicate that there might be multiple alternates in a repository. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates [2]: https://github.com/git-lfs/git-lfs/pull/1007/files
2018-07-09 15:28:23 +00:00
Rename default branch in tests to "main" Currently, our default branch in tests is "master". This is the Git default, but the Git default will likely change in the future, so it makes sense to update our testsuite to be explicit about the branch name. We'll ensure this continues by building against older versions of Git as well as newer versions. We use "main" for the new branch name, since that's the proposed value upstream. This commit was made entirely by automated means using the following command: git grep -l master t | xargs sed -i -e 's/master/main/g'
2020-06-29 16:18:57 +00:00
GIT_TRACE=1 git lfs fetch origin main 2>&1 | tee fetch.log
fs: support multiple object alternates Like in upstream Git, Git LFS supports "object database alternates" (described in [1]) to link several object databases together. We have supported this feature since [2] but read the entire .git/objects/info/alternates in one single buffer via ioutil.ReadFile and checked if a directory existed at that location. If a user specified multiple alternates, then this will fail. Git LFS will look for a directory that has newlines in it, when what it should be doing is splitting that list by the '\n' character and checking each directory if it exists. Let's do that, and also return a []string, instead of a single string, to indicate that there might be multiple alternates in a repository. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates [2]: https://github.com/git-lfs/git-lfs/pull/1007/files
2018-07-09 15:28:23 +00:00
[ "0" -eq "$(grep -c "sending batch of size 1" fetch.log)" ]
)
end_test
begin_test "alternates (commented)"
(
set -e
reponame="alternates-commented-alternate"
setup_remote_repo_with_file "$reponame" "a.txt"
pushd "$TRASHDIR" > /dev/null
clone_repo "$reponame" "${reponame}_alternate"
popd > /dev/null
rm -rf .git/lfs/objects
alternate="$TRASHDIR/${reponame}_alternate/.git/objects"
echo "# $alternate" > .git/objects/info/alternates
Rename default branch in tests to "main" Currently, our default branch in tests is "master". This is the Git default, but the Git default will likely change in the future, so it makes sense to update our testsuite to be explicit about the branch name. We'll ensure this continues by building against older versions of Git as well as newer versions. We use "main" for the new branch name, since that's the proposed value upstream. This commit was made entirely by automated means using the following command: git grep -l master t | xargs sed -i -e 's/master/main/g'
2020-06-29 16:18:57 +00:00
GIT_TRACE=1 git lfs fetch origin main 2>&1 | tee fetch.log
fs: support multiple object alternates Like in upstream Git, Git LFS supports "object database alternates" (described in [1]) to link several object databases together. We have supported this feature since [2] but read the entire .git/objects/info/alternates in one single buffer via ioutil.ReadFile and checked if a directory existed at that location. If a user specified multiple alternates, then this will fail. Git LFS will look for a directory that has newlines in it, when what it should be doing is splitting that list by the '\n' character and checking each directory if it exists. Let's do that, and also return a []string, instead of a single string, to indicate that there might be multiple alternates in a repository. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates [2]: https://github.com/git-lfs/git-lfs/pull/1007/files
2018-07-09 15:28:23 +00:00
[ "1" -eq "$(grep -c "sending batch of size 1" fetch.log)" ]
)
end_test
begin_test "alternates (quoted)"
(
set -e
reponame="alternates-quoted-alternate"
setup_remote_repo_with_file "$reponame" "a.txt"
pushd "$TRASHDIR" > /dev/null
clone_repo "$reponame" "${reponame}_alternate"
popd > /dev/null
rm -rf .git/lfs/objects
t: make alternates test work on Windows This test works fine on Unix systems, but fails on Windows. This occurs because the MSYS environment uses Unix-style paths, but Git wants Windows-style paths in its environment and alternates files. Convert the paths to an appropriate format to ensure this test passes on Windows as well.
2019-08-14 13:49:43 +00:00
# Normally, a plain native_path call would be sufficient here, but when we
# use a quoted alternate, Git interprets backslash escapes, and Windows path
# names look like backslash escapes. As a consequence, we switch to forward
# slashes to avoid misinterpretation.
alternate=$(native_path "$TRASHDIR/${reponame}_alternate/.git/objects" | sed -e 's,\\,/,g')
fs: support multiple object alternates Like in upstream Git, Git LFS supports "object database alternates" (described in [1]) to link several object databases together. We have supported this feature since [2] but read the entire .git/objects/info/alternates in one single buffer via ioutil.ReadFile and checked if a directory existed at that location. If a user specified multiple alternates, then this will fail. Git LFS will look for a directory that has newlines in it, when what it should be doing is splitting that list by the '\n' character and checking each directory if it exists. Let's do that, and also return a []string, instead of a single string, to indicate that there might be multiple alternates in a repository. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates [2]: https://github.com/git-lfs/git-lfs/pull/1007/files
2018-07-09 15:28:23 +00:00
echo "\"$alternate\"" > .git/objects/info/alternates
Rename default branch in tests to "main" Currently, our default branch in tests is "master". This is the Git default, but the Git default will likely change in the future, so it makes sense to update our testsuite to be explicit about the branch name. We'll ensure this continues by building against older versions of Git as well as newer versions. We use "main" for the new branch name, since that's the proposed value upstream. This commit was made entirely by automated means using the following command: git grep -l master t | xargs sed -i -e 's/master/main/g'
2020-06-29 16:18:57 +00:00
GIT_TRACE=1 git lfs fetch origin main 2>&1 | tee fetch.log
fs: support multiple object alternates Like in upstream Git, Git LFS supports "object database alternates" (described in [1]) to link several object databases together. We have supported this feature since [2] but read the entire .git/objects/info/alternates in one single buffer via ioutil.ReadFile and checked if a directory existed at that location. If a user specified multiple alternates, then this will fail. Git LFS will look for a directory that has newlines in it, when what it should be doing is splitting that list by the '\n' character and checking each directory if it exists. Let's do that, and also return a []string, instead of a single string, to indicate that there might be multiple alternates in a repository. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates [2]: https://github.com/git-lfs/git-lfs/pull/1007/files
2018-07-09 15:28:23 +00:00
[ "0" -eq "$(grep -c "sending batch of size 1" fetch.log)" ]
)
end_test
fs/fs.go: support alternates from environment variable The Git documentation also mentions that the "$GIT_ALTERNATE_OBJECT_DIRECTORIES" environment variable is a valid way to configure object database remotes [1]: 2. You could be using the `objects/info/alternates` or `$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to borrow objects from other object stores. Let's support the same by using the last commit, taking in a handle on the operating-system configuration and using that in addition to the list found in .git/objects/info/alternates. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates
2018-07-09 16:23:27 +00:00
begin_test "alternates (OS environment, single)"
(
set -e
reponame="alternates-environment-single-alternate"
setup_remote_repo_with_file "$reponame" "a.txt"
pushd "$TRASHDIR" > /dev/null
clone_repo "$reponame" "${reponame}_alternate"
popd > /dev/null
rm -rf .git/lfs/objects
Ensure proper alternate handling with gitobj There are two ways to specify an alternate in Git: via the repository file or via the environment. gitobj recently learned how to accept the contents of an environment variable and use it, so pass the environment variable when creating a new object database. When performing a fetch, we don't use the object scanner, but we do when performing a push. To make sure that we're exercising the object scanner and gitobj adequately, simulate a push using alternates as well.
2019-07-25 19:29:13 +00:00
rm -rf .git/objects/*
git init
fs/fs.go: support alternates from environment variable The Git documentation also mentions that the "$GIT_ALTERNATE_OBJECT_DIRECTORIES" environment variable is a valid way to configure object database remotes [1]: 2. You could be using the `objects/info/alternates` or `$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to borrow objects from other object stores. Let's support the same by using the last commit, taking in a handle on the operating-system configuration and using that in addition to the list found in .git/objects/info/alternates. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates
2018-07-09 16:23:27 +00:00
t: make alternates test work on Windows This test works fine on Unix systems, but fails on Windows. This occurs because the MSYS environment uses Unix-style paths, but Git wants Windows-style paths in its environment and alternates files. Convert the paths to an appropriate format to ensure this test passes on Windows as well.
2019-08-14 13:49:43 +00:00
alternate="$(native_path "$TRASHDIR/${reponame}_alternate/.git/objects")"
fs/fs.go: support alternates from environment variable The Git documentation also mentions that the "$GIT_ALTERNATE_OBJECT_DIRECTORIES" environment variable is a valid way to configure object database remotes [1]: 2. You could be using the `objects/info/alternates` or `$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to borrow objects from other object stores. Let's support the same by using the last commit, taking in a handle on the operating-system configuration and using that in addition to the list found in .git/objects/info/alternates. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates
2018-07-09 16:23:27 +00:00
GIT_ALTERNATE_OBJECT_DIRECTORIES="$alternate" \
GIT_TRACE=1 \
Rename default branch in tests to "main" Currently, our default branch in tests is "master". This is the Git default, but the Git default will likely change in the future, so it makes sense to update our testsuite to be explicit about the branch name. We'll ensure this continues by building against older versions of Git as well as newer versions. We use "main" for the new branch name, since that's the proposed value upstream. This commit was made entirely by automated means using the following command: git grep -l master t | xargs sed -i -e 's/master/main/g'
2020-06-29 16:18:57 +00:00
git lfs fetch origin main 2>&1 | tee fetch.log
fs/fs.go: support alternates from environment variable The Git documentation also mentions that the "$GIT_ALTERNATE_OBJECT_DIRECTORIES" environment variable is a valid way to configure object database remotes [1]: 2. You could be using the `objects/info/alternates` or `$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to borrow objects from other object stores. Let's support the same by using the last commit, taking in a handle on the operating-system configuration and using that in addition to the list found in .git/objects/info/alternates. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates
2018-07-09 16:23:27 +00:00
[ "0" -eq "$(grep -c "sending batch of size 1" fetch.log)" ]
Ensure proper alternate handling with gitobj There are two ways to specify an alternate in Git: via the repository file or via the environment. gitobj recently learned how to accept the contents of an environment variable and use it, so pass the environment variable when creating a new object database. When performing a fetch, we don't use the object scanner, but we do when performing a push. To make sure that we're exercising the object scanner and gitobj adequately, simulate a push using alternates as well.
2019-07-25 19:29:13 +00:00
GIT_ALTERNATE_OBJECT_DIRECTORIES="$alternate" \
Rename default branch in tests to "main" Currently, our default branch in tests is "master". This is the Git default, but the Git default will likely change in the future, so it makes sense to update our testsuite to be explicit about the branch name. We'll ensure this continues by building against older versions of Git as well as newer versions. We use "main" for the new branch name, since that's the proposed value upstream. This commit was made entirely by automated means using the following command: git grep -l master t | xargs sed -i -e 's/master/main/g'
2020-06-29 16:18:57 +00:00
git lfs push "$(git config remote.origin.url)" main
fs/fs.go: support alternates from environment variable The Git documentation also mentions that the "$GIT_ALTERNATE_OBJECT_DIRECTORIES" environment variable is a valid way to configure object database remotes [1]: 2. You could be using the `objects/info/alternates` or `$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to borrow objects from other object stores. Let's support the same by using the last commit, taking in a handle on the operating-system configuration and using that in addition to the list found in .git/objects/info/alternates. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates
2018-07-09 16:23:27 +00:00
)
end_test
begin_test "alternates (OS environment, multiple)"
(
set -e
reponame="alternates-environment-multiple-alternates"
setup_remote_repo_with_file "$reponame" "a.txt"
pushd "$TRASHDIR" > /dev/null
clone_repo "$reponame" "${reponame}_alternate_stale"
rm -rf .git/lfs/objects
popd > /dev/null
pushd "$TRASHDIR" > /dev/null
clone_repo "$reponame" "${reponame}_alternate"
popd > /dev/null
rm -rf .git/lfs/objects
Ensure proper alternate handling with gitobj There are two ways to specify an alternate in Git: via the repository file or via the environment. gitobj recently learned how to accept the contents of an environment variable and use it, so pass the environment variable when creating a new object database. When performing a fetch, we don't use the object scanner, but we do when performing a push. To make sure that we're exercising the object scanner and gitobj adequately, simulate a push using alternates as well.
2019-07-25 19:29:13 +00:00
rm -rf .git/objects/*
git init
fs/fs.go: support alternates from environment variable The Git documentation also mentions that the "$GIT_ALTERNATE_OBJECT_DIRECTORIES" environment variable is a valid way to configure object database remotes [1]: 2. You could be using the `objects/info/alternates` or `$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to borrow objects from other object stores. Let's support the same by using the last commit, taking in a handle on the operating-system configuration and using that in addition to the list found in .git/objects/info/alternates. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates
2018-07-09 16:23:27 +00:00
t: make alternates test work on Windows This test works fine on Unix systems, but fails on Windows. This occurs because the MSYS environment uses Unix-style paths, but Git wants Windows-style paths in its environment and alternates files. Convert the paths to an appropriate format to ensure this test passes on Windows as well.
2019-08-14 13:49:43 +00:00
alternate_stale="$(native_path "$TRASHDIR/${reponame}_alternate_stale/.git/objects")"
alternate="$(native_path "$TRASHDIR/${reponame}_alternate/.git/objects")"
fs/fs.go: support alternates from environment variable The Git documentation also mentions that the "$GIT_ALTERNATE_OBJECT_DIRECTORIES" environment variable is a valid way to configure object database remotes [1]: 2. You could be using the `objects/info/alternates` or `$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to borrow objects from other object stores. Let's support the same by using the last commit, taking in a handle on the operating-system configuration and using that in addition to the list found in .git/objects/info/alternates. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates
2018-07-09 16:23:27 +00:00
sep="$(native_path_list_separator)"
GIT_ALTERNATE_OBJECT_DIRECTORIES="$alternate_stale$sep$alternate" \
GIT_TRACE=1 \
Rename default branch in tests to "main" Currently, our default branch in tests is "master". This is the Git default, but the Git default will likely change in the future, so it makes sense to update our testsuite to be explicit about the branch name. We'll ensure this continues by building against older versions of Git as well as newer versions. We use "main" for the new branch name, since that's the proposed value upstream. This commit was made entirely by automated means using the following command: git grep -l master t | xargs sed -i -e 's/master/main/g'
2020-06-29 16:18:57 +00:00
git lfs fetch origin main 2>&1 | tee fetch.log
fs/fs.go: support alternates from environment variable The Git documentation also mentions that the "$GIT_ALTERNATE_OBJECT_DIRECTORIES" environment variable is a valid way to configure object database remotes [1]: 2. You could be using the `objects/info/alternates` or `$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to borrow objects from other object stores. Let's support the same by using the last commit, taking in a handle on the operating-system configuration and using that in addition to the list found in .git/objects/info/alternates. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates
2018-07-09 16:23:27 +00:00
[ "0" -eq "$(grep -c "sending batch of size 1" fetch.log)" ]
Ensure proper alternate handling with gitobj There are two ways to specify an alternate in Git: via the repository file or via the environment. gitobj recently learned how to accept the contents of an environment variable and use it, so pass the environment variable when creating a new object database. When performing a fetch, we don't use the object scanner, but we do when performing a push. To make sure that we're exercising the object scanner and gitobj adequately, simulate a push using alternates as well.
2019-07-25 19:29:13 +00:00
GIT_ALTERNATE_OBJECT_DIRECTORIES="$alternate_stale$sep$alternate" \
Rename default branch in tests to "main" Currently, our default branch in tests is "master". This is the Git default, but the Git default will likely change in the future, so it makes sense to update our testsuite to be explicit about the branch name. We'll ensure this continues by building against older versions of Git as well as newer versions. We use "main" for the new branch name, since that's the proposed value upstream. This commit was made entirely by automated means using the following command: git grep -l master t | xargs sed -i -e 's/master/main/g'
2020-06-29 16:18:57 +00:00
git lfs push "$(git config remote.origin.url)" main
fs/fs.go: support alternates from environment variable The Git documentation also mentions that the "$GIT_ALTERNATE_OBJECT_DIRECTORIES" environment variable is a valid way to configure object database remotes [1]: 2. You could be using the `objects/info/alternates` or `$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to borrow objects from other object stores. Let's support the same by using the last commit, taking in a handle on the operating-system configuration and using that in addition to the list found in .git/objects/info/alternates. [1]: https://git-scm.com/docs/gitrepository-layout#gitrepository-layout-objectsinfoalternates
2018-07-09 16:23:27 +00:00
)
end_test
Reference in New Issue Copy Permalink