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
6
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.Setgroups([]int{gid}); err != nil {
   return err
  }

  if err := syscall.Setgid(gid); err != nil {
   return err
  }
  if err := syscall.Setuid(uid); err != nil {
   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 :

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

Arguably fixed?

Michael Vogt (mvo) on 2015-08-25
Changed in snappy:
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for Snappy 15.04 because there has been no activity for 60 days.]

Launchpad Janitor (janitor) wrote :

[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 report contains Public information  Edit
Everyone can see this information.

Other bug subscribers