Moonraker update not working with 3rd party repo/branches correctly - wipes data and links back to main/master. about moonraker

[Arksine]

I will need you to attach log files that reproduce and show this behavior to diagnose what exactly is going on. The first image shows a repo that is marked as invalid because it is dirty, not because of a branch mismatch. A branch mismatch should not invalidate a repo, however there was a brief period of time where the newest version of Mainsail would show it as a warning. What isn't clear to me is if the repo is showing as dirty after the update or showing the aforementioned warning. It also isn't clear to me how the repo in the screenshot got modified to begin with, is there some application or script modifying this repo?

FWIW, a soft recovery should fix a dirty repo. A hard recovery re-clones the repo, you will end up on whatever the default branch of the repo is. Moonraker doesn't switch the branch after a clone, it must be done via the CLI.

[Arksine]

As an addendum I just did the following on the latest Moonraker commit:

• Cloned your klipper_elements repo
• Switched to the troodon_2.0 branch
• Reset the HEAD back 3 commits so an available update will be detected
• Added the following configuration to my test instance of Moonraker:

[update_manager elements]
type: git_repo
channel: dev
primary_branch: troodon_2.0
origin: https://github.com/tinymachines3d/klipper_elements.git
path: /home/eric/klipper_elements
is_system_service: False

I then used Moonraker to update the repo via mainsail and it worked as expected.

[Arksine]

As no one has been able to provide further feedback I'm going to close this. If you are still having issues I recommend asking for assistance on the Klipper Discourse.