Where can I find info on this?
I did an update of all elements and in the completion window it gives you a list of what it did and then I had a few hints. You cannot do anything with them in this window so I simply copied them. I would like to know more about these but in the documentation I cannot find specific reference to these.
hint: Pulling without specifying how to reconcile divergent branches is
07:03:17
hint: discouraged. You can squelch this message by running one of the following
07:03:17
hint: commands sometime before your next pull:
07:03:17
hint:
07:03:17
hint: git config pull.rebase false # merge (the default strategy)
07:03:17
hint: git config pull.rebase true # rebase
07:03:17
hint: git config pull.ff only # fast-forward only
07:03:17
hint:
07:03:17
hint: You can replace “git config” with “git config --global” to set a default
07:03:17
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
07:03:17
hint: or --ff-only on the command line to override the configured default per
07:03:17
hint: invocation.
I tried searching on some of the terms but nothing comes back that looks relevant.
What should I do with these?
The update procedures use git commands during the updates.
Apparently, something has happened that git did not like, and it gave you some hints to avoid it in the future.
As to why this has happened and whether you now might have a problem, it is unfortunately beyond my mastery of the dark git lore.
If it is beyond you my dear Sineos, we need the all knowing oracle of klipper. But being a mere mortal myself, I don’t dare to conjure him up
My brother, who is a Red Hat linux engineer, amongst many other linux related magic, claims he knows what it is, but he is currently on another mission so I have to wait before I can share it here.
To avoid any issues you could try to git reset --hard origin/master and if this does not work, then take the brute force approach of deleting and re-cloning the repositories.
Brother says the following:
Git uses local and remote repo’s. It will try to keep them synced to prevent conflicts. Local repo’s are supposed to be read only. changes on the local side are not allowed to go to the server, only from the server to local.
In my instance git found a local repo which have changes that git does not understand how to deal with, as such it gives hints as to how to prevent those in the future.
Unfortunately it does not tell us which part or repo caused the problem, just indicates the problem, which could be anywhere. It will be hard to find exactly what that was unless you are very deeply involved in these git commands.
In my case the update was successful, and all my elements indicate they are up to date. I am now printing a part to see how it does and it will either fail or be a success.
I will not worry too much until info comes my way that clearly shows I will have to solve this.
Thank you for your reply as always. If it fails I will be back
ok so a swift update, sorry it took a while but my daughter came from the uk for one week and occupied my mancave.
Unfortunately the printer threw a wobbly after this update and those hints. it started to throw random retracts between layer changes without doing a deretract afterwards, thus resulting in fails because it would poop noting for a while before filling up the hotend again. it also would retract too far depending on the duration of the layer because it would retract 10mm and if it only had lets say 3 mm to extrude, it would throw another 10 mm retract and so eventually it would get outside the heatbreak and either get stuck or wrap itself around the extruder gears. it also stopped logging log files correctly. I could not find any logfiles of any of the test prints I did to find out what happened. the last correct logfile was from before the update and a print that finished correctly. I tried the same file again but it would finish the first layer and start to do a 10 mm retract out of the blue.
So I concluded it is time I take the dreaded plunge and rebuild my machine with a cnc frame pieces I bought a while ago but never fitted, install the canbus and the cartographer as well, and do my own whole klipper from fresh. get rid of all the horrible things the original builder had made and which I never fully understood or agreed with. so today my daughter is flying home again and I will start the dissasembly of my voron v2.4. after the rebuild, if it all goes well, I will also register for a serial number. I think if I managed all this ok and the machine is back up and running, I am allowed to call it my own
Anyways if I run into trouble, and undoubtedly I will, I will start a new thread and hope somebody knows what I done wrong.
See you later I am sure.
Kees
