Closed jwhite closed 3 weeks ago
This issue is likely due to your MMU files that are attempting to be backed up but are symbolic links, when you look at your backup repo is there a folder that looks to be hyperlinked to a location that doesn't exist?
When the script tries to pull the repo back down it is probably viewing those locations as empty/corrupt as they have no data.
Could you try what Staubgeborener suggests here: https://github.com/Staubgeborener/Klipper-Backup/issues/121#issuecomment-2345459135 and see if you get the same errors with the files ignored.
I would make sure to use a new empty repo as well for the test.
This is one of the best examples why I add this "I promise that i use markdown syntax" checkbox. Please don't just check this box and that's it - use markdown
to make this stuff readable.
This is one of the best examples why I add this "I promise that i use markdown syntax" checkbox. Please don't just check this box and that's it - use
markdown
to make this stuff readable.
You should specify "Use markdown when including logs as the introduce special characters."
Just found out that there is actually an attribute that can be set to just render it into a codeblock automagically, so will make that change later.
This is one of the best examples why I add this "I promise that i use markdown syntax" checkbox. Please don't just check this box and that's it - use
markdown
to make this stuff readable.You should specify "Use markdown when including logs as the introduce special characters."
No, i would love to see markdown backticks `` everywhere which is code related, including snippets, as it increases readability for everything - not just for log outputs due to special characters. That's just the cherry on top. But like @Tylerjet already told, we know rendering markdown automatically in debug output. Btw what about your original problem, have you found or tested anything yet?
This issue is stale because it has been open for 14 days with no activity.
This issue was closed because it has been inactive for 14 days since being marked as stale.
Code of Conduct
code
more readable which helps to fix the problem and that I have tested the--fix
command mentioned above without success.What happened
First backup triggered normally from the shell works.
Subsequent backups fail with this error :
error: object file .git/objects/16/f3809f603034562731dc0eb244ad696acbf125 is empty fatal: loose object 16f3809f603034562731dc0eb244ad696acbf125 (stored in .git/objects/16/f3809f603034562731dc0eb244ad696acbf125) is corrupt
Subsequent backups don't occur with no warning to the user.
This is endlessly repeatable with a long history of occurring.
~/klipper-backup/script.sh --fix Works temporarily, as it deletes the backup folder.
What did you expect to happen
Backups to occur.
How to reproduce
Installed with all backup options available, but this appears to be using the backup on boot when it fails.
Have uninstalled and reinstalled repeatedly.
Debug
Additional information
No response