Please describe the problem.
Syncing with a special remote "borg" seems to fail - sometimes, but not always.
What steps will reproduce the problem?
I honestly do not know the steps to reproduce this issue. I wish I could. There is one call exiting with a failure (see the debug log), although I don't know which command is being executed before that.
What version of git-annex are you using? On what operating system?
git-annex version: 10.20240129
Debian Stable 12.5
Please provide any additional information below.
...
[2024-05-23 22:39:40.999733121] (Utility.Process) process [57508] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","diff","--cached","--name-only","-z","--diff-filter=ACMRT","--","."]
[2024-05-23 22:39:41.001888748] (Utility.Process) process [57508] done ExitSuccess
[2024-05-23 22:39:41.002613093] (Utility.Process) process [57509] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","symbolic-ref","-q","HEAD"]
[2024-05-23 22:39:41.003662566] (Utility.Process) process [57509] done ExitSuccess
[2024-05-23 22:39:41.004051234] (Utility.Process) process [57510] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","refs/heads/main"]
[2024-05-23 22:39:41.005913975] (Utility.Process) process [57510] done ExitSuccess
Auf Branch main
nichts zu committen, Arbeitsverzeichnis unverändert
[2024-05-23 22:39:41.016177898] (Utility.Process) process [57493] done ExitFailure 1
ok
...
[2024-05-23 22:39:56.926564597] (Utility.Process) process [57484] done ExitSuccess
[2024-05-23 22:39:56.92713831] (Utility.Process) process [57523] done ExitSuccess
sync: 1 failed
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)
Definately, git-annex is my Nr.1 tool for managing my files. There is no comparable alternative out there as of right now. Keep up the good work!
It would be very helpful to know what command is exiting nonzero. Here's how to find out.
Fist, find the line showing the ExitFailure:
Then look above that point in the debug log to find the process with the same number. In the example above, it is 57493. This will show what command was run.
Also, it seems to me that git-annex would usually output some kind of error message if something failed during a sync, and you've omitted the git-annex output. It would be helpful to see that too.
This here is the full git-annex error message:
And the only command that is "failing"
The git commit -am is "failing" (Exit Code 1), because there is nothing to commit. The working directory is clean.
So everything is fine?
I think that "list borg failed" does indicate there is some real failure involving borg, but it seems it's not as simple as a command that fails.
I wonder if this might be caused by your locale settings. git-annex does run
borg listwith LANG=C, but there might be some other locale setting that is breaking it.But... I'm having difficulty seeing how git-annex could fail like that without displaying an error message at all.
I've disabled the subdir option (git annex enableremote borg subdir=) and that seems to solve the issue. That is weird, because the subdir is included in the borg repository. Hmm...
I'm also getting
list borg failedwhen I rungit annex sync borg. In my case, syncing succeeds after creating the first borg archive but fails when the borg repo contains a second archive.I'm running:
To reproduce this problem:
From the debug output the first time running
git-annex sync, the only ExitFailure line:And the first appearance of process 79595:
Only once, after running the command a second time, I got the following additional lines:
I have set
LANG=Candgit annex enableremote borg subdir=as suggested in this thread to no avail.Thanks in advance for your help! I have used and loved git-annex for years and am very thankful for the work Joey and others have put into it. I'm planning to buy a git-annex backpack soon.