Update All Does not Perform Update #204

Closed
opened 2022-06-02 16:22:55 +02:00 by LifeDay · 6 comments
LifeDay commented 2022-06-02 16:22:55 +02:00 (Migrated from github.com)

Linux Distribution

Raspbian GNU/Linux 10 (buster) armv7l

What happened

Update menu shows there are updates for Klipper and Moonraker.
Selecting update all does not perform an update but displays the message, "Everything is already up-to-date!"

What did you expect to happen

I would have expected Klipper and Moonraker to be updated

How to reproduce

  1. Launch Kiauh
  2. Select menu 2) [Update]
  3. Menu shows updates for Klipper and Moonraker are available
  4. Select option a) [Update all]
  5. Message shows "Everything is already up-to-date!"
    BEEN2VrL0L

Additional information

The menu is also loading slowly and in a staggered fashion that I don't remember from a week or so ago.

### Linux Distribution Raspbian GNU/Linux 10 (buster) armv7l ### What happened Update menu shows there are updates for Klipper and Moonraker. Selecting update all does not perform an update but displays the message, "Everything is already up-to-date!" ### What did you expect to happen I would have expected Klipper and Moonraker to be updated ### How to reproduce 1. Launch Kiauh 2. Select menu **2) [Update]** 3. Menu shows updates for Klipper and Moonraker are available 4. Select option a) [Update all] 5. Message shows "Everything is already up-to-date!" ![BEEN2VrL0L](https://user-images.githubusercontent.com/11354683/171651070-44aa0922-0425-4703-8a57-c91007aa89b7.png) ### Additional information The menu is also loading slowly and in a staggered fashion that I don't remember from a week or so ago.
LifeDay commented 2022-06-02 20:30:28 +02:00 (Migrated from github.com)

Updating each separately seems to work.
However, moonraker did not successfully restart. I think it said something about moonraker.service not existing.
I think that might be related to having multiple moonraker instances running for multiple printers.

Updating each separately seems to work. However, moonraker did not successfully restart. I think it said something about moonraker.service not existing. I think that might be related to having multiple moonraker instances running for multiple printers.
JRHeaton commented 2022-06-02 22:04:40 +02:00 (Migrated from github.com)

I'm experiencing the same issue, and also with a multi-instance installation.

I'm experiencing the same issue, and also with a multi-instance installation.
dw-0 commented 2022-06-03 21:19:52 +02:00 (Migrated from github.com)

i was able to reproduce that issue and im working on a solution. not sure why that broke...

i was able to reproduce that issue and im working on a solution. not sure why that broke...
jangrewe commented 2022-06-15 20:02:35 +02:00 (Migrated from github.com)

Yup, can confirm all of the above.

Yup, can confirm all of the above.
JRHeaton commented 2022-06-28 00:34:51 +02:00 (Migrated from github.com)

Still observing this issue in the latest update

Still observing this issue in the latest update
dw-0 commented 2022-06-30 11:10:27 +02:00 (Migrated from github.com)

The issue should be solved now.
The slower loading than before might still occur, i have to address that in another issue and try to improve the performance on loading the update menu. Im not quite sure what i did, that made the menu load slower now.

The issue should be solved now. The slower loading than before might still occur, i have to address that in another issue and try to improve the performance on loading the update menu. Im not quite sure what i did, that made the menu load slower now.
Sign in to join this conversation.