Hi,
I’m facing forced switching from 4G to 3G on my new USB Dongle, so as result the network slow down a bit for short time. And when that happens It returns this
Is there any workaround for that matter?
1 Like
ogra
April 30, 2021, 7:44am
2
It looks like this could be similar to:
We have devices running snaps in some pretty remote locations with poor connectivity. Sometimes we observe that during refresh, snap downloads error out - with an “unexpected EOF” error.
Doing a refresh manually on a particular device in Sierra Leone, I observe that the ~50MB download chugs along fine for a while at ~25kB/sec, but then about a quarter of the way through the dreaded “unexpected EOF” comes up and everything drops dead.
error: cannot perform the following tasks:
- Download snap "…
and there seems to be work on a fix as well:
canonical:master
← fujimotos:sf/snapd-slow-conn
opened 01:06AM - 30 Apr 21 UTC
Snapd uses `LimitTime(90*time.Second)` as a retry policy. For
this reason, it o… nly recovers from network errors occurring
within initial 90 seconds.
This policy makes snapd unusable on slow network. For example,
suppose that a WFH user, with an intermittent home network,
are trying to do this:
$ snap install libreoffice
this command can take a few hours. And if any (temporal) network
occurs midway, snapd would just abort the task, throwing away all
the `.partial` snap files it fetched so far.
This removes the LimitTime() policy, so that snapd can recover
from any temporal error on a long downloading task.
Signed-off-by: Fujimoto Seiji <fujimoto@ceptord.net>
1 Like