[00:29] <davecheney> wow, trying to find somethign that _wont_ marshall into yaml is more complicated than I thought
[00:32] <davecheney> urgh
[00:32] <davecheney> thumper: menn0 http://paste.ubuntu.com/13205113/
[00:32]  * thumper looks
[00:32] <davecheney> yaml.Marshal returns an error
[00:32] <davecheney> but the code panics ...
[00:32]  * menn0 looks
[00:33] <thumper> heh
[00:33] <thumper> because... reasons
[00:35] <davecheney> https://github.com/go-yaml/yaml/issues/144
[00:35] <davecheney> so, to test that writeyaml fails on invalid yaml
[00:35] <davecheney> i have to
[00:35] <davecheney> a. find some invalid yaml
[00:36] <davecheney> b. find some invalid yaml that doesn't crash the library
[00:36] <davecheney> \o/
[00:36] <davecheney> i've checked yaml.v1 and yaml.v2
[00:37] <menn0> davecheney: it looks like panics that are yamlErrors will be turned into errors
[00:37] <menn0> and all others will be allowed to paniuc
[00:38] <menn0> the whole yamlError thing is a crappy way of allowing deeply nested encoding calls to abort the whole process immediately
[00:38] <menn0> a way to get around Go not having exceptions
[00:38] <davecheney> i'm discovering why this function had not test coverage ...
[00:40] <menn0> davecheney: if that panic were a call to the package's fail() func, an error would be returned
[00:49] <davecheney> https://github.com/juju/utils/pull/172
[01:38] <wallyworld_> thumper: could i beg for a small review to address a windows test failure https://github.com/juju/charmrepo/pull/43
[03:15] <wallyworld> thumper: tyvm for the review
[03:16] <thumper> np
[03:17] <thumper> sorry for the delay, was otp for 1:1s
[03:19] <wallyworld> np, long meeting :-)
[03:21] <menn0> thumper: logging doc updates: http://reviews.vapour.ws/r/3091/
[03:21] <thumper> wallyworld: no, just four in a row
[03:21] <wallyworld> allover and done with  for the week :-)
[04:43] <menn0> thumper: super quick one: http://reviews.vapour.ws/r/3093/
[04:44] <thumper> done
[04:49] <thumper> menn0: hmm
[04:49] <thumper> 88 files changed, +1,050 −2,330
[04:49] <thumper> http://reviews.vapour.ws/r/3094/
[04:50] <thumper> holy shitballs batman
[04:50] <thumper> I felt it was bad, but didn't realise it was that bad
[04:52] <menn0> thumper: good net line delta though
[04:52] <thumper> hmm... diff is off
[04:52] <thumper> includes previous branch...
[04:53] <thumper> which I though landed already
[04:53] <thumper> this will explain a lot
[04:54] <menn0> thumper: right
[04:54] <menn0> i've got to stop now but might jump back later to review
[04:54] <thumper> not sure why the diff is bad
[04:54] <thumper> don't bother
[04:54] <thumper> I'm stopping too
[04:54] <menn0> i want to get a few other things squared away as well
[04:57] <thumper> menn0: that's better, 43 files,  +98 −1,375
[04:57] <thumper> now I'm done
[04:58] <thumper> laters folks
[05:53] <davecheney> http://reviews.vapour.ws/r/3095/
[05:53] <davecheney> anyone for a little one ?
[09:25] <wallyworld> fwereade: morning to you. did you have a few minutes to spare a sunburnt bread thief?
[09:34] <fwereade> wallyworld, heyhey
[09:34] <fwereade> sure, joining our hangout
[09:35] <wallyworld> fwereade: on my way
[09:36] <wallyworld> anastasiamac: https://plus.google.com/hangouts/_/canonical.com/ian-william
[10:02] <frobware> fwereade, standup?
[10:34] <frobware> voidspace, ping, 1:1?
[10:34] <voidspace> frobware: omw
[14:15] <mup> Bug #1514444 opened: Windows github.com/juju/juju/cmd/jujud/dumplogs/dumplogs.go:65: undefined <blocker> <ci> <regression> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1514444>
[14:51] <mup> Bug #1514451 opened: TestUniterConfigChangedHook fails <ci> <intermittent-failure> <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1514451>
[14:51] <mup> Bug #1514456 opened: Juju is unable to detach root volume <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1514456>
[14:54] <mup> Bug #1514451 changed: TestUniterConfigChangedHook fails <ci> <intermittent-failure> <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1514451>
[14:54] <mup> Bug #1514456 changed: Juju is unable to detach root volume <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1514456>
[14:57] <mup> Bug #1514451 opened: TestUniterConfigChangedHook fails <ci> <intermittent-failure> <test-failure> <windows> <juju-core:Triaged> <https://launchpad.net/bugs/1514451>
[14:57] <mup> Bug #1514456 opened: Juju is unable to detach root volume <intermittent-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1514456>
[14:57] <mup> Bug #1514462 opened: Assertion failure in TestAPI2ResultError <ci> <test-failure> <juju-core:Triaged> <https://launchpad.net/bugs/1514462>
[15:05] <katco> ericsnow: ut
[15:05] <katco> ?
[15:37] <katco> dimitern: ping, hey do you think you're going to wrap up bug 1483879 soon?
[15:37] <mup> Bug #1483879: MAAS provider: terminate-machine --force or destroy-environment don't DHCP release container IPs <bug-squad> <destroy-machine> <landscape> <maas-provider>
 <juju-core:Triaged> <juju-core 1.24:In Progress by dimitern> <juju-core 1.25:In Progress by dimitern> <https://launchpad.net/bugs/1483879>
[15:38] <dimitern> katco, yes
[15:38] <dimitern> katco, I need another review on it
[15:39] <katco> dimitern: ok, cool :) just trying to figure out if bugsquad moonstone needed to pick it up
[15:39] <dimitern> and was having lots of maas issues, but managed to verify most of the cases at least manually
[15:39] <katco> nice
[15:47] <katco> wwitzel3: hey before you get too far into that bug, can you rebase/merge master into our lxd branch so we can get a bless and prepare for landing?
[15:47] <katco> wwitzel3: "<sinzui> katco: cimmit 1c86f86 is what you want to merge."
[15:47] <wwitzel3> katco: sure
[15:48] <katco> wwitzel3: ty
[15:49] <dimitern> frobware, voidspace, dooferlad, can you please review http://reviews.vapour.ws/r/3088/ ?
[15:49] <dooferlad> dimitern: *click*
[15:49] <voidspace> dimitern: in a bit if no-one gets to it. Got my head stuck in a bug right now.
[15:50] <dimitern> voidspace, sure, np
[15:51] <voidspace> fixed the test failure I had, now stuck in a different one *grrr*
[15:57] <fwereade> voidspace, do I remember you having familiarity with the rsyslog stuff?
[15:58] <fwereade> voidspace, wondering if you know why the worker apparent deletes the rsyslog config file when the worker stops
[15:58] <voidspace> !!!!!
[15:58] <voidspace> fwereade: no
[15:58] <voidspace> fwereade: it's changed a lot since I worked on it apparently
[15:59] <voidspace> fwereade: I don't think that was done by wwitzel3 and I when we worked on it
[16:00] <voidspace> blame would know though...
[16:00] <fwereade> voidspace, yeah, that's all axw's code from about 18 months ago
[16:01] <fwereade> voidspace, and he probably did it for a reason, but I'm not clear what that reason might be, thought you might have already gone through the digging process
[16:02] <fwereade> voidspace, np, I'll ask him tonight, it's not critical
[16:02] <voidspace> cool
[16:02] <fwereade> voidspace, and moot soon enough what with db-log \o/
[16:02] <alexisb> hey all, happy monday
[16:02] <natefinch> fwereade: that sounds like the code to clean up the agent stuff... there was a bug about that happening when you sigkilled the agent
[16:03] <alexisb> cherylj, katco anything urgent I should be aware of?
[16:03] <alexisb> crawling through the inbox after being out :)
[16:03] <cherylj> alexisb: nothing new that I can think of
[16:03] <cherylj> alexisb: you feeling better today?
[16:03] <fwereade> natefinch, ooh, if there's a reported bug associated I can be a bit grumpier about it ;p
[16:03] <alexisb> cherylj, much! thank you
[16:04] <natefinch> fwereade: I would search for it, but I think i'm being bitten by the launchpad "feature" where it's not searching across series
[16:05] <katco> alexisb: nope
[16:07] <katco> alexisb: glad you're feeling better :)
[16:08] <alexisb> thanks katco
[16:08] <alexisb> thanks to you and the team for keeping things moving in my absence
[16:12] <wwitzel3> katco: I rebased that commit in to our branch, but I'm not sure where it goes now
[16:12] <wwitzel3> katco: there is still conflicts against current master that need to be resolved
[16:13] <katco> wwitzel3: i.e. you're having trouble resolving the conflicts?
[16:13] <wwitzel3> katco: so not sure what to make the PR against
[16:13] <wwitzel3> katco: no, that hash is rebased
[16:13] <wwitzel3> katco: but that hash isn't the current HEAD of master
[16:14] <katco> wwitzel3: oh right. so you've got 1 pr up against the lxd feature branch right?
[16:14] <wwitzel3> katco: no, I rebased, so it won't merge against our feature branch
[16:14] <katco> wwitzel3: ah i see now
[16:15] <katco> wwitzel3: gosh... not actually sure how github handles that? if you propose against the feature branch what does it say? just merge conflicts?
[16:15] <frobware> dimitern, will also take a look in a bit
[16:15] <wwitzel3> katco: yeah, unable to merge
[16:15] <wwitzel3> katco: which makes sense, since I rewrote history
[16:16] <katco> wwitzel3: right
[16:16] <katco> wwitzel3: hrm. maybe just use git to push directly into the FB?
[16:16] <dimitern> frobware, ta!
[16:16] <katco> wwitzel3: and do a force?
[16:17] <katco> ericsnow: natefinch: any opinions on how to tackle this?
[16:17] <frobware> dimitern, I started looking then realised it was quite large and I /think/ I now know why one of my tests fails..
[16:17] <dimitern> frobware, yeah? what was it?
[16:17] <frobware> dimitern, (ha, don't ask). :)
[16:18] <wwitzel3> katco: yeah, I had to force push to my copy of the feature branch to get it up, so the merge exists under my namespace right now
[16:18] <dimitern> frobware, ok :)
[16:18] <katco> wwitzel3: b/c the point is to get a bless of the FB, so skipping the tests might be OK
[16:18] <frobware> dimitern, it was one of those... If only I had taken the dog for a walk earlier... type of bugs. :)
[16:18] <wwitzel3> katco: right, makes sense
[16:19] <dimitern> frobware, right :)
[16:20] <natefinch> wwitzel3, katco: maybe make a new branch off the feature branch and cherry pick what you need (if it's not too many changes). I've had success with that in the past when I get into a bad spot
[16:20] <wwitzel3> natefinch: we need .. a lot
[16:21] <wwitzel3> katco: I don't have permission to do a force anyway ;)
[16:21] <katco> wwitzel3: lol i can take care of it if we think that's the way to go
[16:25] <wwitzel3> katco: well, I could just merge it instead of rebasing
[16:25] <natefinch> katco, wwitzel3: force push onto the feature branch is fine if no one else has outstanding branches against it
[16:25] <katco> wwitzel3: yeah we can do that too. rebasing is nice if we have to come back to anything later, but if it's this much of a PITA maybe merging is the way to go
[16:26] <wwitzel3> I would just force push the feature
[16:26] <katco> wwitzel3: ok. i'll take care of that then
[16:26] <wwitzel3> you brought it up, this is for getting blessed
[16:26] <katco> wwitzel3: ty for rebasing
[16:26] <wwitzel3> katco: np
[16:27] <wwitzel3> very minor, mostly dep.tsv nags
[16:28] <natefinch> fwereade: gota minute to talk? I found another odd bug in my unitassigner code.   Machines weren't getting created with sequential ids (i.e. I'd get 0, 1, 3, 8..)  Any immediate thoughts in what might cause that?
[16:29] <wwitzel3> natefinch: just add "machine number assignment no longer sequental" to the release notes, feature shipped ;)
[16:29] <natefinch> lol
[16:33] <natefinch> rogpeppe: did you have a script for automating the import sorting (i.e. project internal vs. project external)?
[16:33] <rogpeppe> natefinch: yeah
[16:33] <rogpeppe> natefinch: github.com/rogpeppe/sortimports
[16:33] <fwereade> natefinch, huh
[16:34] <fwereade> natefinch, yes, for some reason st.sequence() is getting called too often
[16:34] <fwereade> natefinch, ideally when you know you need to create a machine you consume a sequence number just once and pass that into the txn-builder loop
[16:35] <fwereade> natefinch, possibly one slipped into a createMachineOps  that was hitting failure a it later? or something?
[16:36] <natefinch> fwereade: sounds plausible
[17:02] <dooferlad> dimitern, frobware, voidspace: hangout
[17:03] <katco> wwitzel3: your rebased branch is here? git@github.com:wwitzel3/juju.git
[17:06] <wwitzel3> katco: yeah, lxd-provider
[17:06] <katco> wwitzel3: k
[17:18] <voidspace> dammit
[17:24] <voidspace> frobware: dooferlad: dimitern: if you have time http://reviews.vapour.ws/r/3097/
[17:27] <cherylj> frobware: Did someone from your team get a chance to look at bug 1512371?
[17:27] <mup> Bug #1512371: Using MAAS 1.9 as provider using DHCP  NIC will prevent juju bootstrap <bug-squad> <maas-provider> <network> <juju-core:Triaged> <https://launchpad.net/bugs/1512371>
[17:27] <frobware> cherylj, nope
[17:29] <frobware> cherylj, but we talked about dimiter's wip branch which help fix this: https://github.com/dimitern/juju/tree/maas-1.25-better-bridge-script
[17:30] <cherylj> frobware: okay, so that should address that issue as well?
[17:31] <frobware> cherylj, should do / can do, but wasn't specifically started for that bug though.
[17:31] <frobware> cherylj, the bug came after dimitern started work on that
[17:31] <katco> wwitzel3: can you tal at this: https://github.com/juju/juju/pull/3694
[17:32] <katco> wwitzel3: i can't force into FB, so did a merge --theirs of your branch
[17:32] <katco> wwitzel3: and would like to land that into FB
[17:32] <katco> wwitzel3: just need a sanity check
[17:33] <cherylj> frobware: ah, okay.  so that branch was just for improving things, and not for a specific bug?
[17:34] <frobware> cherylj, correct. the issue is that the current script changes the order of what's in /e/n/i. the branch script is more complicated and attempts to change things in-situ
[17:35] <wwitzel3> katco: looking
[17:36] <cherylj> frobware: is there a target for landing that branch?   We'll probably want to make sure we pull that in when we do 1.25.1
[17:36] <frobware> cherylj, initially we said master
[17:36] <wwitzel3> katco: yeah, that looks like it did the right thing to me
[17:36] <katco> wwitzel3: k merging
[17:37] <cherylj> frobware: it looks like that branch is based off of 1.25?
[17:40] <natefinch> gah, I've somehow disabled the scroll wheel in sublime :/
[17:41] <natefinch> ...nope I've disabled both the scroll wheel and right click
[18:15] <perrito666> how ennerving, a place that does one of the best croissants in the city makes also one of the worse coffees
[18:17] <natefinch> heh
[18:17] <perrito666> this country would really beneffit from discovering donuts :p
[18:17] <natefinch> haha
[18:55] <natefinch> ....and reboot fixes it.
[19:10] <cmars> anyone here familiar with dumplogs to review http://reviews.vapour.ws/r/3100/ ?
[19:10] <cmars> i'm not familiar with juju-dumplogs but windows seems to feel left out
[19:13] <mup> Bug #1514555 opened: local provider "machine0" agent fails to start up on wily if "/var/lib" is not on the "/" partition.  <juju-core:New> <https://launchpad.net/bugs/1514555>
[19:16] <mup> Bug #1514555 changed: local provider "machine0" agent fails to start up on wily if "/var/lib" is not on the "/" partition.  <juju-core:New> <https://launchpad.net/bugs/1514555>
[19:22] <mup> Bug #1514555 opened: local provider "machine0" agent fails to start up on wily if "/var/lib" is not on the "/" partition.  <juju-core:New> <https://launchpad.net/bugs/1514555>
[20:04] <mup> Bug #1514570 opened: 'JUJU_DEV_FEATURE_FLAGS=address-allocation' blocks after first 3 ips are allocated <juju-core:New> <https://launchpad.net/bugs/1514570>
[20:07] <mup> Bug #1514570 changed: 'JUJU_DEV_FEATURE_FLAGS=address-allocation' blocks after first 3 ips are allocated <juju-core:New> <https://launchpad.net/bugs/1514570>
[20:19] <mup> Bug #1514570 opened: 'JUJU_DEV_FEATURE_FLAGS=address-allocation' blocks after first 3 ips are allocated <juju-core:New> <https://launchpad.net/bugs/1514570>
[21:13] <natefinch> katco: good news, both bugs with unit assignment were from the same source, and I have a fix for it.
[21:14] <katco> natefinch: nice!
[21:51] <natefinch> uh, how do un-revert a PR?  I tried re-PRing with the same old branch with some added fixes, and only the fixes are getting applied, not the whole of the branch... which means the unit assigner code is not getting added back to master
[21:52]  * natefinch wonders if he should revert the revert PR...
[21:55] <natefinch> I got it.. just cherry-picked the original merge
[22:00] <natefinch-afk> katco, wwitzel3, ericsnow_: if you guys have time... the fixes are very small: (easier to see on github) http://reviews.vapour.ws/r/3103/
[22:00] <natefinch-afk> ^ https://github.com/juju/juju/pull/3698
[22:00] <wwitzel3> natefinch-afk: ok, i'll take a look
[22:15] <thumper> rick_h__: ping
[22:19] <rick_h__> thumper: pong
[22:19] <thumper> rick_h__: hey there
[22:19] <thumper> rick_h__: wheren't we going to talk this week about CLI stuff?
[22:19] <thumper> I thought you were going to make some meetings
[22:20] <rick_h__> thumper: yes I was/am
[22:20] <thumper> k
[22:20] <rick_h__>  thumper will get them on tonight sorry for the delay
[22:20] <thumper> that's fine
[22:20] <thumper> it isn't like I've got nothing to do :)
[22:20] <rick_h__> thumper: thanks fornthe poke
[22:20] <thumper> np
[22:21] <rick_h__> heh +1
[22:36] <katco> natefinch-afk: wwitzel3: ericsnow_: as you EOD, be sure to update any bugs you're working on
[22:36] <ericsnow_> katco: k
[22:39] <rick_h__> thumper: added please adjust if those don't work out
[22:40] <thumper> rick_h__: can we move tomorrows one out 30 minutes?
[22:40] <thumper> rick_h__: I'm normally at the gym between 12 and 1
[22:40] <rick_h__> thumper: wfm
[22:40] <thumper> cheers
[22:41] <thumper> alexisb: why is the TL call this week on a different day?
[22:41] <alexisb> thumper, becuase weds is a US holiday
[22:41] <thumper> ah
[22:42] <alexisb> thumper, hopefully I actually changed this weeks meeting and not some random day in dec ;)
[23:32] <wwitzel3> katco: yep, will do, thanks for the reminded
[23:32] <wwitzel3> reminder