Comment 1 for bug 1998022

Hi. Thank you for reporting this bug. I tried to reproduce this, with both of a fresh install and a refresh, and had some mixed results. It seems like snapd will usually resume the download from the point it stopped, if the network is cut. However, I was able to see it going back to the beginning once. It could be that the time limit or the retry limit is reached. This warrants further investigation.
The "download too slow: 0.00 bytes/sec" error message also seems to suggests that in a period of 5 minutes nothing was downloaded. Was the network out for 5 minutes or was it out for just a short period of time and snapd didn't resume for 5 minutes?
Regarding the second problem of partial files being deleted, that is intended because it prevents partial files from taking up disk space, if the download was cancelled, too slow, etc. Interrupted downloads should be resumed in the same operation so this shouldn't be a problem.
Can you paste the output of `snap version` and attach the snapd.log file created by running `journalctl -u snapd > snapd.log` here please?

Thank you,
Miguel