Closed yarikoptic closed 1 year ago
@yarikoptic
process seems to try to
git rm
file which isn't there
The code always removes an asset that needs to be updated before updating it. If the asset doesn't exist, the --ignore-unmatch
option should mean that git rm
does nothing and exits successfully.
@yarikoptic The asset in question is now present in the 000341 backup.
@yarikoptic
process seems to try to
git rm
file which isn't thereThe code always removes an asset that needs to be updated before updating it. If the asset doesn't exist, the
--ignore-unmatch
option should mean thatgit rm
does nothing and exits successfully.
ah, right, but then why it actually "returned non-zero exit status 128" ?
@yarikoptic The asset in question is now present in the 000341 backup.
cool, but how did you get there? why my invocation didn't?
@yarikoptic
ah, right, but then why it actually "returned non-zero exit status 128" ?
Because the repo was locked.
cool, but how did you get there? why my invocation didn't?
I didn't do anything. The backup was automatically updated by the time I got to it.
ah, right, but then why it actually "returned non-zero exit status 128" ?
Because the repo was locked.
locked by what if lock file didn't exist?
I didn't do anything. The backup was automatically updated by the time I got to it.
ah, ok.
@yarikoptic
locked by what if lock file didn't exist?
I don't know, but it's possible that the lock was undone before fuser
ran.
ok, so the mystery will remain on why it crashed to start with -- hypothetically what processes managed to lock it which lead to error
fuser
shouldn't be called if index file is not even theregit rm
file which isn't therenothing to commit, working tree clean