diff options
Diffstat (limited to 'doc/bugs')
3 files changed, 58 insertions, 1 deletions
diff --git a/doc/bugs/initremote_doesn__39__t_work_in_scripts.mdwn b/doc/bugs/initremote_doesn__39__t_work_in_scripts.mdwn new file mode 100644 index 000000000..75361a6c1 --- /dev/null +++ b/doc/bugs/initremote_doesn__39__t_work_in_scripts.mdwn @@ -0,0 +1,25 @@ +### Please describe the problem. + + +### What steps will reproduce the problem? + +Run "git-annex initremote" from an environment (cron, CI, etc.) where /dev/tty doesn't exist. + +### What version of git-annex are you using? On what operating system? + +git-annex version: 6.20160613-g35dbe35 on debian jessie + +### Please provide any additional information below. + +Example of the error @ https://gitlab.com/DanielDent/git-annex-remote-rclone/builds/2166644 + +Error: +gpg: cannot open tty `/dev/tty': No such device or address + +failed + +Rumour on the internets is that the "--no-tty" parameter to GPG may fix the problem. + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) + +Yes! It's great! diff --git a/doc/bugs/race_condition_with___39____39__git-annex__58___Cannot_run_git-annex-remote-__33__dne__33___--_Make_sure_it__39__s_in_your_PATH_and_is_executable.__34__.mdwn b/doc/bugs/race_condition_with___39____39__git-annex__58___Cannot_run_git-annex-remote-__33__dne__33___--_Make_sure_it__39__s_in_your_PATH_and_is_executable.__34__.mdwn new file mode 100644 index 000000000..156f75b36 --- /dev/null +++ b/doc/bugs/race_condition_with___39____39__git-annex__58___Cannot_run_git-annex-remote-__33__dne__33___--_Make_sure_it__39__s_in_your_PATH_and_is_executable.__34__.mdwn @@ -0,0 +1,19 @@ +### Please describe the problem. + +When git-annex has not recently used a remote, there appears to be a race condition where sometimes it will fail with "git-annex: Cannot run git-annex-remote-!dne! -- Make sure it's in your PATH and is executable." + +### What steps will reproduce the problem? + +This test script will trigger it: https://gitlab.com/DanielDent/git-annex-remote-rclone/blob/demo-race-condition/.gitlab-ci.yml +Output: https://gitlab.com/DanielDent/git-annex-remote-rclone/builds/2167279 + +This test script works: https://gitlab.com/DanielDent/git-annex-remote-rclone/blob/demo-race-condition-2/.gitlab-ci.yml + +But the reason it works is because it's using "git-annex testremote GA-rclone-CI --fast || git-annex testremote GA-rclone-CI --fast" - it fails the first time, and then works the second time. +Output: https://gitlab.com/DanielDent/git-annex-remote-rclone/builds/2167316 + +This test script doesn't trigger it: https://gitlab.com/DanielDent/git-annex-remote-rclone/blob/master/.gitlab-ci.yml +Output: https://gitlab.com/DanielDent/git-annex-remote-rclone/builds/2166902 + +The 'git-annex copy test --to GA-rclone-CI' line prior to the 'testremote' invocation seems to warm caches and avoids having the bug trigger. + diff --git a/doc/bugs/v6_appears_to_not_thin.mdwn b/doc/bugs/v6_appears_to_not_thin.mdwn index 7d9deb5ef..2cadcedc4 100644 --- a/doc/bugs/v6_appears_to_not_thin.mdwn +++ b/doc/bugs/v6_appears_to_not_thin.mdwn @@ -41,7 +41,20 @@ Debian 8.5 repo config file: -[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [annex] uuid = c5c203ec-9353-4213-8af5-6fcb8de36ca2 version = 6 thin = true [filter "annex"] smudge = git-annex smudge %f clean = git-annex smudge --clean %f +[core] +repositoryformatversion = 0 +filemode = true +bare = false +logallrefupdates = true + +[annex] +uuid = c5c203ec-9353-4213-8af5-6fcb8de36ca2 +version = 6 +thin = true + +[filter "annex"] +smudge = git-annex smudge %f +clean = git-annex smudge --clean %f |