parsed xml submission has blank snap information
Bug #1719406 reported by
Sheila Miguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Next Generation Checkbox (CLI) |
Fix Released
|
Medium
|
Sylvain Pineau |
Bug Description
Some submissions are appearing with one snap, and that snap has no information.
Here's an example in staging, but there are also examples in production.
https:/
After downloading the xml, I used checkbox-support to parse it and the submission info from that is:
{u'type': u'set-snap-
u'version': None,
u'install-date': None,
u'confinement': None,
u'developer': None,
u'revision': None,
u'channel': None,
u'name': ''
}]}
Related branches
~sylvain-pineau/plainbox:fix-1719406
- Paul Larson: Approve
-
Diff: 44 lines (+4/-4)2 files modifiedplainbox/impl/providers/exporters/data/checkbox.json (+2/-2)
plainbox/impl/providers/exporters/data/hexr.xml (+2/-2)
affects: | checkbox-support → plainbox |
Changed in plainbox: | |
importance: | Undecided → Medium |
assignee: | nobody → Sylvain Pineau (sylvain-pineau) |
milestone: | none → 0.38.0 |
status: | Triaged → In Progress |
Changed in plainbox: | |
status: | In Progress → Fix Committed |
Changed in plainbox: | |
milestone: | 0.38.0 → 0.39.0 |
affects: | plainbox → checkbox-ng |
Changed in checkbox-ng: | |
milestone: | 0.39.0 → none |
milestone: | none → 1.0.0 |
Changed in checkbox-ng: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We had to supply at least one fake object to both snap and package resource jobs as tests depending on a particular snap/deb package used to fail when nothing was reported by resources. hence this dummy snap.
But this fix [1] could be enough to stop faking one object per resource (snap and package). TBC and if it works, we could see a 0 count to really match what's installed on the system.
[1] https:/ /code.launchpad .net/~sylvain- pineau/ plainbox/ +git/plainbox/ +merge/ 326929