Occasionally I’ll publish snaps to the store, and the store will return error 504. While simply resubmitting the snap isn’t much of a problem, I’m curious as to whether there’s any identifiable reason as to what the error is, it’s just mildly irritating. And since I’m naturally lazy, this often happens in the context of CI where the entire build process gets repeated, often for hours at a time.
This mostly happens with one of my snaps in particular, it’s a fairly large snap (1.3GB) but smaller than some other snaps that don’t seem to suffer as badly. The snap is called
root-framework, and with the nightly builds, about 10% of them just never deploy because the store returns an error.
Occasionally however, there’ll be scenarios like today where the package needs rebuilding to pull in security updates, and the same track fails to publish repeatedly (at the time of writing this, we’re on attempt 4!), e.g:
These are all cases of the build going fine, but the store rejecting the submission after reaching 100% upload.
This isn’t an isolated incident, it’s been happening for a long time, but I thought it might be worth bringing it up just incase there is something that can be done on the store side. Otherwise, maybe Snapcraft could be updated to retry uploads a few times before aborting & etc.
Is there anything that stands out as problematic with large snaps or this snap in particular?