-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial backup fails as files are not added to commit #129
Comments
i see towards the bottom that git prints out your token as |
Thanks for the quick reply. Yes, it is actually set. I removed my token it from the output of `script.sh --debug" before posting. |
ahh ok, when installing did you use install.sh to configure settings or did you edit the .env manually? |
I used It's still strange as it at least should commit the |
could you run with --debug again and post that, as i see in the initial one it didn't print out things like your .git/config file, etc... since it didn't get created until the script ran. |
Yeah my wondering is that there are some addtional git errors about pushing/accessing the remote repo so if those resolve the rest might too |
Okay, here's what I found:
Very strange |
Sure. Here's the output for modifying it to explicitly only add
|
ok and then can you do one with klipper-backup reset to the latest commit so we can see the error when it tries to add and push the printer_data |
also after line 221 can you put
that should let us see what files it actually tries to copy over to the backup_config folder |
Oh okay now I get what you mean.
Sure, here it is:
So this means klipper-backup reads and copies the files correctly but git doesn't seem add them to the commit, right? |
okay can you do
and then run script.sh again |
Already tried that (and tried again after you said it). Nothing changed. However, if I run the script again after removing
Executed a second time:
|
hrmm something is not right as it shouldn't be trying to check out a commit in printer_data/config |
can you completely remove the klipper-backup folder and config_backup.
and then redownload and rerun install.sh |
I'm wondering if something didn't clone properly or copy over during the install.sh process |
also i would use a fresh git repository that is completely empty on this next test just to eliminate the old one having issues as well |
That was my idea, too, so I'm already doing this right now. |
Oh my f'ing god. The answer was so simple. I actually had a local git repository initialized in my config folder. I can't remember doing that but it I may have done that in the past by accident. I checked multiple times but didn't add the Sorry for this and thank you very much for your effort in finding a solution! |
Ahhhh dang that was going to be my next question about doing ls -la in there, I'm working (albeit slowly) on some stuff in the restore branch for catching any .git repos and popping up some warnings for instances like that. |
Code of Conduct
What happened
After I installed Klipper-Backup according to the docs I tried to do an initial backup using
./script.sh
. However, an error message appears.What did you expect to happen
I expected it to confirm that my config has been uploaded to GitHub
How to reproduce
Install first, then run
./script.sh
Debug
Additional information
I'm aware that it says "Error: no GitHub repo bliepp/Ender3-Klipper-Config found (maybe private)". However, changing it to public didn't change anything (the message became "The GitHub repo bliepp/Ender3-Klipper-Config exists (public)" but the error didn't go away, though).
The text was updated successfully, but these errors were encountered: