search

SanaaHamel / nevermore-controller

GNU Affero General Public License v3.0
95 stars 13 forks source link

Update Manager indicating "Unknown" #10

Open stefanpieter opened 5 months ago

stefanpieter commented 5 months ago

After the latest Nevermore update via Mainsail, the update manager, the status is indicated as "Unknown." Once updated, Klipper was not able to connect to the MCU.

v0.14-1-ge58cbabb

I manually updated as per the dummies guide

It now connects; however, the "Known" status remains in the update manager.

Screenshot 2024-04-03 at 21 47 19

[update_manager nevermore]
type: git_repo
path: ~/nevermore-controller
origin: https://github.com/sanaahamel/nevermore-controller.git
primary_branch: main
is_system_service: False
SanaaHamel commented 5 months ago

Once updated, Klipper was not able to connect to the MCU.

Insufficient information, would need printer log for details. Common cause: 2.4 GHz interference, see FAQ.

It now connects; however, the "Known" status remains in the update manager.

Can reproduce. This is an issue with Mainsail. Looking at the WS data coming from moonraker, it all looks sane. Reading the code suggests it might be upset with semver.valid rejecting v0.14-1, which isn't a valid semver according to the spec, but I also don't have any problems with my other tracked packages which do have equivalently 'malformed' version numbers according to the spec... Maybe @meteyou can provide insight?

stefanpieter commented 5 months ago

As requested.

klippy (23).log moonraker (4).log