[upload] Fix backtrace when cancelling upload

[jcastill]

This commit fix a backtrace that appears when
the user cancels a file upload after authentication.

Related: RHEL-94968

---

Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines

• Is the commit message split over multiple lines and hard-wrapped at 72 characters?
• Is the subject and message clear and concise?
• Does the subject start with [plugin_name] if submitting a plugin patch or a [section_name] if part of the core sosreport code?
• Does the commit contain a Signed-off-by: First Lastname email@example.com?
• Are any related Issues or existing PRs properly referenced via a Closes (Issue) or Resolved (PR) line?
• Are all passwords or private data gathered by this PR obfuscated?

[packit-as-a-service]

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

• sudo yum install -y dnf-plugins-core on RHEL 8
• sudo dnf install -y dnf-plugins-core on Fedora
• dnf copr enable packit/sosreport-sos-4057
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

[jcastill]

I was thinking about adding a general exception after KeyboardInterrupt to capture any other uncatched exceptions. Any thoughts on this?

[arif-ali]

Might as well, of there is a chance for another issue to happen?

[jcastill]

I've tried to come up with possible ways to trigger other exceptions, but haven't found a way to get one yet. Rather, I thought I could add them generally after being explicit with the KeyboardInterrupt one, and if we capture one we can refine it later on (i.e. add a new explicit one before the general one).

[jcastill]

@pmoravec @arif-ali shall I add a general exception catch then and force push? Or do you prefer if I leave it as it's now?

[arif-ali]

if you've tried other means, lets stick with what we have, and we move on