Hi world,
After a over a decade of not daily driving Linux, I tried return recently with the Ubuntu 24.04 release and, unfortunately it looks like that journey will end soon because of hardware instability that makes my main computer useless for any serious work.
What I have noticed before I swap back is a very interesting quirk between Snapcraft Remote-Builds and internet connectivity, at least as far as the newer Snapcraft 8 goes.
For example:
james@James-Desktop:~/joplin-desktop-snap$ snapcraft remote-build
All data sent to remote builders will be publicly available. Are you sure you want to continue? [y/N]: y
remote-build is experimental and is subject to change. Use with caution.
The authorization page:
(*REDACTED*)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
(*about an hour of generic processing*)
snapcraft internal error: gaierror(-3, 'Temporary failure in name resolution')
Full execution log: '/home/james/.local/state/snapcraft/log/snapcraft-20240523-125416.424344.log'
So, one of my instabilities is with the wifi driver. (Classic!). Although the speed of the connection is generally good (coming in at half that at Windows but a solid 5 times faster than the UK average), I randomly lose all connections at once, constantly, every 10-15 minutes. The connections begin working again 20 seconds later, and generally things move on with some curses about why my video is buffering.
However not Snapcraft, I’ve been trying to use remote build to patch a security bug, and every single time on a long enough build I’m not able to finish it.
Older versions of Snapcraft used to provide a build ID that could recover a lost build session. However the new behaviour, in this specific set of circumstances, doesn’t recover the build but restart it entirely.
This is now the third time I’ve waited an hour to have a wifi blip for 20 seconds and Launchpad/Snapcraft delete the previous build entirely rather than continuing it.
Is this the expected behaviour? It feels like a relative niche but the relative consequences here could be dire depending upon situations, and the old behaviour generally never had a problem.