Cancelled backups and uploads leave truncated .img.xz files that cannot be deleted from the UI

[eliasbakken]

Found testing v1.1.0-RC8-2-g23a2bb6 on A8 s/n 0498.

What happens

After cancelling operations, truncated images stay in the install list on the USB drive:

operation	left behind
Backup claude-backup-test, cancelled at 3%	claude-backup-test.img.xz, 60 751 872 B
File upload, cancelled at 75%	claude-cancel-test.img.xz, 235 929 600 B

The integrity check does its job: selecting either gives the red X and Install stays disabled. But the files stay forever, taking space, and the UI has no way to remove them.

Backup: a plain bug

cancelBackup does os.Remove(images_folder + "/" + state.Filename), i.e. .../claude-backup-test. backup-emmc writes ${OUTFILE}.img.xz. The remove targets a file that never exists.

Upload

uploadCancel never removes the partial file. Maybe that is deliberate (#118 relies on the integrity check), but then there needs to be a delete.

Also

• After the backup cancel, the open tab's image list did not show the new partial file until a reload.
• Suggest: delete partial files on cancel in both paths, and add a delete action for images in the list.

[eliasbakken]

Fixed in #158 (merged as d611c55). cancelBackup removed , which never exists - backup-emmc writes .img.xz - so the truncated image stayed (6d0329d); cancelled and failed uploads now remove theirs too (38ab823); and /api/delete_image plus a Delete button can remove any image, which nothing could before (7553fcf).

Checked on A8 0498: cancelled backups and uploads leave nothing behind, and delete removed four leftover images and refused ../options.cfg.