bug: missing moonraker restart after patching update manager #225

Closed
opened 2022-07-21 13:42:26 +02:00 by dw-0 · 0 comments
dw-0 commented 2022-07-21 13:42:26 +02:00 (Migrated from github.com)

It is required to run a moonraker restart after/inside those functions.

ae011963da/scripts/mainsail.sh (L571)

ae011963da/scripts/fluidd.sh (L397)

ae011963da/scripts/klipperscreen.sh (L204)

ae011963da/scripts/moonraker-telegram-bot.sh (L460)

Otherwise the modified moonraker.conf will not be applied immediately and users have to restart moonraker themself before they are able to see the components listed in clients update manager.

It is required to run a moonraker restart after/inside those functions. https://github.com/th33xitus/kiauh/blob/ae011963da3fb93ee94d8f8e32ec0c5387b05b1c/scripts/mainsail.sh#L571 https://github.com/th33xitus/kiauh/blob/ae011963da3fb93ee94d8f8e32ec0c5387b05b1c/scripts/fluidd.sh#L397 https://github.com/th33xitus/kiauh/blob/ae011963da3fb93ee94d8f8e32ec0c5387b05b1c/scripts/klipperscreen.sh#L204 https://github.com/th33xitus/kiauh/blob/ae011963da3fb93ee94d8f8e32ec0c5387b05b1c/scripts/moonraker-telegram-bot.sh#L460 Otherwise the modified moonraker.conf will not be applied immediately and users have to restart moonraker themself before they are able to see the components listed in clients update manager.
Sign in to join this conversation.