You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As witnessed on the forums here there's currently insufficient logging in case of failures in running update checks, e.g. GitHub release fetching with an outdated PAT. The "available" version simply stays empty without any log message to indicate why.
Describe the solution you'd like
A failing request should at least cause a log entry, not just a silent error. That would allow easier debugging of a failure to check for updates. Better yet would be to log the reason for the error in the frontend, like with rate limiting situations. Something like "Backend request failed, see log" would already be more helpful than the current sitation.
Is your feature request related to a problem? Please describe.
As witnessed on the forums here there's currently insufficient logging in case of failures in running update checks, e.g. GitHub release fetching with an outdated PAT. The "available" version simply stays empty without any log message to indicate why.
Describe the solution you'd like
A failing request should at least cause a log entry, not just a silent error. That would allow easier debugging of a failure to check for updates. Better yet would be to log the reason for the error in the frontend, like with rate limiting situations. Something like "Backend request failed, see log" would already be more helpful than the current sitation.
Describe alternatives you've considered
No response
Additional context
https://community.octoprint.org/t/not-being-offered-upgrades/38829
The text was updated successfully, but these errors were encountered: