[02:20] <wallyworld> axw: sorry, finger slipped :-)
[02:20] <axw> wallyworld: bye :p
[04:13]  * thumper is done
[04:14] <thumper> laters
[09:02] <dooferlad> dimitern: hangout?
[09:03] <voidspace> dimitern: http://reviews.vapour.ws/r/1970/
[10:38] <dimitern> TheMue, LGTM
[10:43] <TheMue> dimitern: thx
[10:44] <voidspace> dooferlad: thanks
[11:48] <voidspace> dooferlad: failing tests, so I'll have to investigate and resubmit
[11:48] <voidspace> dooferlad: on my branch (thought I'd run the tests - but obviously not)
[11:53] <dimitern> voidspace, TheMue, dooferlad, guys, I'm not feeling well and need to get some rest, so I might be back later in the evening
[11:53] <TheMue> dimitern: oh, hope you'll get well soon
[11:54] <dimitern> thanks
[13:00] <rogpeppe> anyone know how to bootstrap a local provider without apt-get installing juju-local
[13:00] <rogpeppe> ?
[13:00] <rogpeppe> i really don't want to have juju-local installed because i never ever want to use /usr/bin/juju
[13:01] <rogpeppe> fwereade: ^ ?
[13:01] <fwereade> rogpeppe, afraid not
[13:01] <fwereade> rogpeppe, I don't mind having a /usr/bin/juju hanging around :)
[13:01] <rogpeppe> fwereade: problem is, i can remove /usr/bin/juju but it keeps on *coming back*
[13:02] <rogpeppe> fwereade: i like being able to do go install juju/... and then running "juju". it always surprises me when it chooses /usr/bin/juju
[13:02] <mgz> rogpeppe: curtis has a fake juju-local package
[13:02] <mgz> that you can install, plus the real deps of juju-local
[13:02] <rogpeppe> mgz: ha, that would be great (although, wtf!)
[13:03] <rogpeppe> ISTM that juju should check for the actual deps it needs, not juju-local per se
[13:03] <fwereade> rogpeppe, to be fair it's not optimal: I do have a mild `ll $(which juju)` habit
[13:03] <rogpeppe> mgz: know where i can get it from?
[13:04] <mgz> trying to find it again
[13:04] <rogpeppe> mgz: ta
[13:05] <mgz> rogpeppe: forwarded you mail
[13:05] <rogpeppe> mgz: thanks!
[13:06] <mgz> I presume it still works, is a hack from a year ago
[13:06]  * rogpeppe tries to remember how to install debs directly
[13:06] <mgz> dpkg -i
[13:07] <rogpeppe> ah dpkg
[13:07] <rogpeppe> i should do it more often
[13:11] <rogpeppe> mgz: thanks, that worked nicewly
[13:11] <rogpeppe> nicely, even
[13:11] <mup> Bug #1464356 changed: TestCloudInit fails <blocker> <ci> <regression> <test-failure> <juju-core:Invalid> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1464356>
[13:16] <tasdomas> hi
[13:16] <tasdomas> soulc somebody take a look at http://reviews.vapour.ws/r/1116/ and tell me if it's a bad idea?
[13:17] <mgz> is dimitern off today?
[13:17] <mgz> if so, probably want someone else to fix the 1.24 branch
[13:18] <tasdomas> s/soulc/could
[13:18] <mgz> see bug 1464356
[13:18] <mup> Bug #1464356: TestCloudInit fails <blocker> <ci> <regression> <test-failure> <juju-core:Invalid> <juju-core 1.24:Triaged> <https://launchpad.net/bugs/1464356>
[14:00] <natefinch> ug, why the heck does juju/errors/NewErr return a value that does not satisfy the error interface? :/
[14:01] <perrito666> natefinch: because satisfying the interface is too mainstream
[14:02] <natefinch> perrito666: It just means that you can't use that function to directly embed the value into another error type... which is the only reason that function even exists.
[14:03] <katco> natefinch: standup
[14:03] <katco> wwitzel3: not sure if you're here yet, but standup if you are
[14:05] <natefinch> katco: coming'
[15:05] <pmatulis> hello, re restrictions (block/unblock), does an unblock override a restriction set in environments.yaml ?
[15:54] <fwereade> is anyone who worked on status-history aroound?
[15:55] <perrito666> fwereade: I am
[15:56] <fwereade> perrito666, so, we seem to do things quite strangely there
[15:56] <perrito666> tell me
[15:56] <fwereade> perrito666, ISTM that we destroy history before we're finished with it
[15:56] <fwereade> perrito666, and that unit.Destroy now runs 2 transactions in flagrant violantion of sense or sanity
[15:57] <perrito666> fwereade: mmm, destruction of history  was one of the things that I was unsure of
[15:57] <perrito666> fwereade: wanna hangout?
[15:58] <fwereade> perrito666, sure, start one
[15:59] <perrito666> fwereade: come to https://plus.google.com/hangouts/_/canonical.com/tanzanite-stand it is a deserted land at this time of the day
[15:59] <fwereade> perrito666, by which I mean "please, good sir, would you be so kind as to start a hangout and invite me to join it" :)
[16:24] <mup> Bug #1466269 changed: bootstrap instance started but did not change to Deployed <bootstrap> <maas> <windows> <juju-core:New> <https://launchpad.net/bugs/1466269>
[17:32] <natefinch> ericsnow, katco:  I'm not going to be able to get this landed before I get back, which will be in approximately 2 hours.  Sorry, the rebase caused some conflicts, and I evidently did the wrong thing when merging them (i.e. I had removed plugin.go from the process dir in my branch, and it looks like more was added to that file in eric's branch).
[17:32] <ericsnow> natefinch: if you don't mind, I can take a stab at getting it merged...
[17:33] <katco> ericsnow: natefinch: we can wait since our planning meeting is on mon
[17:33] <ericsnow> katco, natefinch: k
[17:33] <natefinch> ericsnow: you're welcome to.
[17:33] <katco> natefinch: but we do need that landed today i think
[17:33] <natefinch> katco: yep
[17:34] <natefinch> katco:  it's a matter of putting back the plugin.go file and removing the launch details struct from it, I believe.
[17:34] <natefinch> ericsnow: ^
[17:34] <ericsnow> natefinch: if it can wait it will probably be better for you to sort it out
[17:34] <natefinch> ericsnow: that's fine
[17:34] <natefinch> I should have time
[17:34] <natefinch> gotta run
[17:34] <ericsnow> natefinch: also, considering merging rather than rebasing
[17:35] <ericsnow> natefinch: take care
[18:03] <mup> Bug #1466951 opened: juju no-proxy does not work with apt-http-proxy <juju-core:New> <https://launchpad.net/bugs/1466951>
[19:06] <moqq> i have the machine-0 jujud agent consuming our entire cpu on both of our environments, independantly
[19:06] <moqq> has anyone here seen this before?
[19:06] <mup> Bug #1466969 opened: Upgrading 1.20.14 -> 1.24.0 fails <canonical-bootstack> <juju-core:New> <https://launchpad.net/bugs/1466969>
[19:09] <perrito666> moqq: not me, is there any logging that we can see?
[19:10] <moqq> after startup everything appears idle from the logs, strace reveals its spending a lot of time on futex
[19:10] <moqq> i can grab the startup logs one sec
[19:11] <moqq> mongo also is spiking a lot with it
[19:11] <perrito666> moqq: juju version?
[19:11] <moqq> less consistently, but there seems to be a lot of activity between them
[19:12] <moqq> 1.23.3-trusty-amd64
[19:22] <moqq> perrito666: https://gist.github.com/tysonmalchow/765ed773a7edfc0a2f96 is the startup log
[19:23] <perrito666> moqq: weird, I see nothing out of the ordniary :(
[19:27] <moqq> :(
[19:28] <moqq> i really dont want ot have to scrap juju 1 month after getting it into our production env… but unless i can fix this we’re going to have to :(
[19:29] <perrito666> moqq: sadly it is friday afternoon so not many people around to help either, if you can hold it is very likely that more of us around could solve your issue
[19:30] <moqq> okay well that’s comforting to hear
[19:31] <perrito666> moqq: though the last link they passed in #juju seems relevant
[19:32] <moqq> yeah i’ve tried as many permutations of the advice on that thread as possible to no avail so far
[19:48] <natefinch> ericsnow: doing the fixup now.  I noticed your LaunchDetails validate method errored if status is empty.... do we really want to error in that case?  Seems like ID should be required, but status is just a nice to have.
[19:50] <ericsnow> natefinch: one key motivation for this feature is to display the current status of a managed workload process, so I'm leaning toward always requiring it
[19:51] <natefinch> ericsnow: fair enough
[19:55] <natefinch> ericsnow: so, thinking about this some more.. it's somewhat problematic.  We've told the plugin to launch a process, and presumably it has.  It has returned an ID, but no status.... returning an error from Launch would probably make the rest of the system think that no process was launched, even though one was.  I'm worried that'll leave people in a weird state.
[19:55] <natefinch> ericsnow: I guess the error from launch would cause whatever hook is firing to go into an error state... which might be good enough, since it should only happen at dev time
[19:56] <natefinch> (hopefully)
[20:00] <ericsnow> natefinch: that sounds right
[20:01] <fwereade> yay, I got the most totalitarian rb id yet
[20:01] <fwereade> http://reviews.vapour.ws/r/1984/
[20:04] <perrito666> fwereade: loooool
[20:05] <natefinch> fwereade: double plus good
[20:06] <mup> Bug #1466984 opened: juju cannot remove-machine even with --force <juju-core:New> <https://launchpad.net/bugs/1466984>
[20:07] <perrito666> means we had at least that amount of reviews in a year
[20:07] <natefinch> perrito666: less than a year, really
[20:07] <perrito666> less?
[20:07] <perrito666> mm true, was around july right?
[20:08] <natefinch> perrito666: something like that... I forget exactly when it went live.. .august even, I thought
[20:08] <natefinch> perrito666: I dunno, it took ericsnow forever to get that thing deployed ;)
[20:08] <perrito666> I do recall we showcased it in the induction sprint for ericsnow and katco
[20:08] <ericsnow> natefinch: :)
[20:09] <perrito666> and at that point it was near the 4th of july because we had this very cool trip to boston with many patriotic things going on
[20:09] <katco> perrito666: ericsnow: we decided to move to RB at my induction sprint. implementation was that winter.
[20:09] <katco> perrito666: ericsnow: sometime between oct.-dec.
[20:09] <mup> Bug #1466984 changed: juju cannot remove-machine even with --force <juju-core:New> <https://launchpad.net/bugs/1466984>
[20:11] <ericsnow> katco, perrito666: first one (mid-September): http://reviews.vapour.ws/r/18/
[20:12] <mup> Bug #1466984 opened: juju cannot remove-machine even with --force <juju-core:New> <https://launchpad.net/bugs/1466984>
[20:15] <natefinch> ericsnow: what do you think about the proc-register command needing to pass the same format as launch returns?  i.e. id and status both in a json blob?
[20:15] <natefinch> ericsnow: would let us reuse more code and keeps the API consistent
[20:15] <ericsnow> natefinch: makes sense
[21:01] <natefinch> ericsnow, katco:  I'm going to have to finish up this merge tonight.... there's just a ton of places where we're using the old process.LaunchDetails that need to be modified to use plugin.ProcDetails.
[21:01] <ericsnow> natefinch: k
[21:01] <natefinch> also ericsnow - env_test.go:80: envSuite.TestUnparseEnvOkay    - this is relying on map ordering... you need to use jc.SameContents
[21:01] <katco> natefinch: k please make sure it gets done
[21:01] <ericsnow> natefinch: k
[21:01] <natefinch> katco: I will.  Sorry, been busting my butt, but there was a lot more to the merge than I had hoped.
[21:02] <natefinch> katco: I have a couple more hours of work time to get it done tonight and I think I'n really close right now.
[21:02] <natefinch> katco: just gott arun for dinner.. natives are restles
[23:16] <mup> Bug #1466984 changed: juju cannot remove-machine even with --force <juju-core:New> <https://launchpad.net/bugs/1466984>