Improve logging, UX for cloud-upload-errors.

One of the reasons this bug (see parent of this commit ... or the issue nr if you have internal access) was so vague is that A. the user was insufficiently prompted, and B. no one could find anything in our logs.

CURA-8004
This commit is contained in:
Remco Burema 2021-04-14 14:30:42 +02:00
parent 9227c303c6
commit 4c5dac0dfd
No known key found for this signature in database
GPG key ID: 215C49431D43F98C
2 changed files with 5 additions and 2 deletions

View file

@ -269,6 +269,8 @@ class CloudOutputDevice(UltimakerNetworkedPrinterOutputDevice):
else:
PrintJobUploadErrorMessage(I18N_CATALOG.i18nc("@error:send", "Unknown error code when uploading print job: {0}", error_code)).show()
Logger.log("w", "Upload of print job failed specifically with error code {}".format(error_code))
self._progress.hide()
self._pre_upload_print_job = None
self._uploaded_print_job = None
@ -279,6 +281,8 @@ class CloudOutputDevice(UltimakerNetworkedPrinterOutputDevice):
Displays the given message if uploading the mesh has failed due to a generic error (i.e. lost connection).
:param message: The message to display.
"""
Logger.log("w", "Upload error with message {}".format(message))
self._progress.hide()
self._pre_upload_print_job = None
self._uploaded_print_job = None