snapcraft and other snap commands don't support a --debug for behind the scenes debugging information
Bug #1784372 reported by
Richard Harding
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
New
|
Undecided
|
Unassigned | ||
snapd |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I was attempting to perform a snapcraft release when the command hung. I killed it after 60s of inactivity. I then tried other snap info commands which did eventually work on 40s response times with truncated responses. I wanted to see what was up so I attempted to use a --debug on the cli in an effort to get an idea of what address/api calls it might be trying to make so I can check network routing details/etc. I was unable to get that info from the command.
I'd love to see this added as it's proven extremely helpful in my Juju cli use to be able to add a --debug and have a step by step guide on what the client is doing in an effort to help me diagnose/debug.
Changed in snapd: | |
importance: | Undecided → Wishlist |
Changed in snapd: | |
status: | New → Triaged |
To post a comment you must log in.
Note I was instructed to setup some sysctl tweaks for this information as noted in
https:/ /forum. snapcraft. io/t/extremely- slow-snap- downloads/ 4668
and can't help but think an easier way would be a bit nicer for everyone.