Merge lp:~therve/landscape-client/package-reporter-errors into lp:~landscape/landscape-client/trunk
Proposed by
Thomas Herve
Status: | Merged |
---|---|
Approved by: | Björn Tillenius |
Approved revision: | 327 |
Merged at revision: | 328 |
Proposed branch: | lp:~therve/landscape-client/package-reporter-errors |
Merge into: | lp:~landscape/landscape-client/trunk |
Diff against target: |
128 lines (+55/-9) 3 files modified
landscape/message_schemas.py (+11/-7) landscape/package/reporter.py (+18/-1) landscape/package/tests/test_reporter.py (+26/-1) |
To merge this branch: | bzr merge lp:~therve/landscape-client/package-reporter-errors |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Björn Tillenius (community) | Approve | ||
Free Ekanayaka (community) | Approve | ||
Review via email: mp+59529@code.launchpad.net |
Description of the change
That part is of course too easy. The reporter just sends a new message when a smart update fails. We need to do something on the server side to handle it. I was thinking about adding an alert?
To post a comment you must log in.
Looks good, +1.
An alert sounds fine, though sometimes the errors might be transient, like an HTTP timeout.