snapcraft push gets no feedback when things fall over server-side

Bug #1776302 reported by John Lenton on 2018-06-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snap Store
Matias Bordese

Bug Description

I recently did a 'snapcraft push' of a snap with a yaml that something store-side didn't like. However, snapcraft didn't report any sort of an error and instead carried on polling forever, because no error was reported; the store side had apparently died with

ReaderError: unacceptable character #x1d42e: special characters are not allowed\n in \"/tmp/tmp55XwRo/unpacked/meta/snap.yaml

but that page was still returning

code: "being_processed",
processed: false,
can_release: false

Bret Barker (noise) on 2018-12-17
Changed in snapstore:
importance: Undecided → Low
Daniel Manrique (roadmr) wrote :

One thing is the store-side task just dying and leaving snapcraft spinning, and the other is the actual problem that caused this particular failure.

So let's scope this bug to "when a PackageScanTask dies, snapcraft just spins forever". Potential solutions include for the status endpoint to more thoroughly check whether the task is in progress or has died, or for the task to write some sort of "I died" thing somewhere where the status endpoint can check it (unsure if a celery task has this kind of "finally" behavior).

I'll file the problem with the invalid character as a separate bug.

Matias Bordese (matiasb) on 2019-07-02
Changed in snapstore:
assignee: nobody → Matias Bordese (matiasb)
status: New → In Progress
Matias Bordese (matiasb) on 2019-07-04
Changed in snapstore:
status: In Progress → Fix Committed
Matias Bordese (matiasb) on 2019-07-11
Changed in snapstore:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers