errors returned by syscall are not user-friendly, should not be shipped raw to the user
Bug #1460658 reported by
John Lenton
on 2015-06-01
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Snappy |
Undecided
|
Unassigned | ||
| | 15.04 |
Undecided
|
Unassigned | ||
Bug Description
code like thise:
if err := syscall.
return err
}
if err := syscall.
return err
}
if err := syscall.
return err
}
needs to wrap all those errors with a more helpful explanation of what we were doing when the error occurred.
| Michael Terry (mterry) wrote : | #1 |
Michael Vogt (mvo)
on 2015-08-25
| Changed in snappy: | |
| status: | New → Incomplete |
| Launchpad Janitor (janitor) wrote : | #2 |
[Expired for Snappy 15.04 because there has been no activity for 60 days.]
| Launchpad Janitor (janitor) wrote : | #3 |
[Expired for Snappy because there has been no activity for 60 days.]
| Changed in snappy: | |
| status: | Incomplete → Expired |
To post a comment you must log in.


This situation got better with https:/ /code.launchpad .net/~chipaca/ snappy/ muppets/ +merge/ 261376
Arguably fixed?