On 06/02/14 14:14, Nate Finch wrote:
One thing I noticed was that it looked like it wasn't generating an
actual stack trace ever. I think that's pretty critical to knowing how
you got to the spot where you got the error.
I made the default behaviour of the error message to match exactly what
Hi Daniele,
That's expected behavior with Amulet, as it caches the charm locally to do
some verification against the charms in the deployment. So it deploys from
local: rather than the charm store.
As for the dataset-size, if 80% isn't a sane value, I'll try various other
default values to make
So, I took a deeper dive into Tim's newly renamed
arrarhttps://godoc.org/github.com/juju/arrarpackage, and compared it
to Roger's
errgohttps://godoc.org/launchpad.net/~rogpeppe/errgo/errors-package/errorspackage.
Before I go into the implementations, I want to write down some goals:
1: Make it
Hi Antonio,
Do you have an ETA or a ticket number for this issue ?
Cheers
Dave
On Wed, Feb 5, 2014 at 3:09 PM, David Cheney david.che...@canonical.comwrote:
Hi Antonio,
Do you have an ETA or a ticket number for this issue ?
Cheers
Dave
On Wed, Feb 5, 2014 at 7:45 AM, David
