Merge branch 'master' of ssh://git-annex.branchable.com

This commit is contained in:
Joey Hess 2021-08-18 16:35:54 -04:00
commit 69c1c0b1cd
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 35 additions and 0 deletions

View file

@ -0,0 +1,20 @@
### Please describe the problem.
```
(git)smaug:/mnt/datasets/datalad/ci/git-annex/builds/2021/08[master]git
$> grep 'prop_parse_build_presence_log' cron-*/build-ubuntu.yaml-*/1_test-annex\ \(normal\).txt
...
cron-20210810/build-ubuntu.yaml-373-69466103-success/1_test-annex (normal).txt:2021-08-10T02:46:59.4799294Z prop_parse_build_presence_log: OK (1.91s)
cron-20210811/build-ubuntu.yaml-374-69466103-success/1_test-annex (normal).txt:2021-08-11T02:47:05.9924579Z prop_parse_build_presence_log: OK (2.09s)
cron-20210812/build-ubuntu.yaml-375-69466103-failed/1_test-annex (normal).txt:2021-08-12T02:49:23.2932499Z prop_parse_build_presence_log: FAIL
... and so on
```
so between those two revisions
```
$> grep 'name:.*8.202108' cron-2021081{1,2}/build-ubuntu.yaml-*/1_test-annex-more.txt
cron-20210811/build-ubuntu.yaml-374-69466103-success/1_test-annex-more.txt:2021-08-11T02:46:49.4682708Z name: git-annex-debianstandalone-packages_8.20210803+git35-g2df44abad_amd64
cron-20210812/build-ubuntu.yaml-375-69466103-failed/1_test-annex-more.txt:2021-08-12T02:48:07.7317675Z name: git-annex-debianstandalone-packages_8.20210803+git45-g6318c0f27_amd64
```

View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="git-annex.branchable.com@78dd096e15e9d37643bf695293cae77fec735698"
nickname="git-annex.branchable.com"
avatar="http://cdn.libravatar.org/avatar/f9a3a021d4457e45fb899b38ba0aed41"
subject="So where are the file stored?"
date="2021-08-18T20:19:25Z"
content="""
This is like a 1000ft overview, but doesn't actually say where the files are actually stored or how they're synchronized.
Does one need to setup a samba, sftp, or AWS bucket to contain the large files? Does a clone of the repo full down all of the large files, or just the files in the working directory that's checked out? Are files transferred via direct connection to other repos (ex the same SSH tunnel that git uses, http, etc) or is there a UDP p2p layer like syncthing or bittorrent that might struggle with certain NAT situations?
The sentence \"A file's content can be transferred from one repository to another by git-annex. Which repositories contain a given value is tracked by git-annex (see location tracking).\" makes it sound like the old versions of the large files only exist on computers that checked out those copies. Does this mean old versions of a file might be lost forever if a single clone is deleted and temporarily unavailable if clones that contain those revisions of the file are offline?
Is there a way to ensure that a clone has all copies of all of the files (for example, when using git with a central trusted server)?
"""]]