[01:23] <wallyworld> axw: thanks for reviews, issues hopefully addressed
[01:23] <axw> wallyworld: looking now
[01:23] <blahdeblah> \o all
[01:23] <blahdeblah> Happy New Year
[01:23] <axw> blahdeblah: hiya, and to you
[01:25] <wallyworld> +1
[01:25] <blahdeblah> Can anyone tell me the name of the API that charms.reactive uses to send data between layers?  Is it charms.reactive.bus?
[01:26] <wallyworld> blahdeblah: not done any reactive charm development, sorry
[01:27]  * blahdeblah asks around elsewhere; apologies for the redundancy for those in multiple channels
[01:41] <wallyworld> axw: thanks for reviews, landing now
[01:41] <axw> wallyworld: cool
[04:29] <axw> wallyworld: are metabox going to come through for you this week?
[04:29] <wallyworld> axw: i sure hope so
[04:30] <wallyworld> they said NYE that order was underway
[04:31] <axw> wallyworld: I'll be interested to see it at the next sprint. probably won't get one though, I don't want a discrete card in my next laptop
[04:31] <axw> dead weight
[04:32] <wallyworld> axw: yeah, +1, but bublebee turns it off. trouble is, to get everything else (alloy case, 4 DDR4 slots, 2 M.2 slots, 2 HHD slots etc etc) that was the only choice without spending double
[08:32] <dimitern> morning!
[08:33] <dimitern> and happy new year :)
[08:47] <anastasiamac> happy new year, dimitern \o/
[08:48] <TheMue> happy new year to my ex-colleagues ;)
[08:49] <dimitern> TheMue, o/
[08:51] <dimitern> dooferlad, frobware, are you guys around today?
[09:14] <dooferlad> dimitern: hi, just got here, new computer running :-D
[09:23] <dimitern> dooferlad, nice! happy new year :)
[09:23] <dooferlad> dimitern: happy new year!
[09:24] <dimitern> dooferlad, I got a 4K monitor and now it works way better with the scaling and the past issues I was having are gone
[09:24] <dimitern> dooferlad, I'd appreciate a look at https://github.com/juju/juju/pull/4029 when you have some time ;)
[09:25] <dooferlad> dimitern: *click* (email can wait)
[09:28] <dimitern> dooferlad, cheers!
[09:52] <dimitern> voidspace, o/ happy new year :)
[09:58] <voidspace> dimitern: same to you :-)
[10:01] <dooferlad> dimitern, voidspace,
[10:01] <dooferlad> dimitern, voidspace: hangout
[10:01] <voidspace> dooferlad: morning
[10:18] <voidspace> dimitern: dooferlad: sorry about that
[10:18] <dooferlad> voidspace: no problem
[10:18] <voidspace> dimitern: dooferlad: so last year I landed the worker that imports spaces, plus fixed some bugs in it, but it has a few TODOs and needs tests
[10:19] <voidspace> dimitern: dooferlad: the last couple of days, when you were off, I spent working with Andy on a MAAS problem
[10:19] <voidspace> dimitern: dooferlad: we probably need to talk to dimitern about that
[10:19] <voidspace> dimitern: dooferlad: but it can wait for frobware
[10:20] <dimitern> voidspace, ok, let's chat when andy's back then
[10:21] <voidspace> dimitern: yep
[10:21] <voidspace> dimitern: this was the DNS settings not being set on container templates, due to the change to manual network interfaces in 1.25
[10:21] <voidspace> dimitern: there is a simple fix, but that seems like a huge change that landed on 1.25
[10:22] <dimitern> voidspace, right! yeah, I remember that
[10:22] <dimitern> voidspace, we're getting far behind master as well :/
[10:23] <voidspace> dimitern: we should merge master
[10:23] <voidspace> dimitern: we'll do it as a merge rather than a rebase though, right?
[10:23] <voidspace> dimitern: I can propose that
[10:23] <dimitern> voidspace, yeah, that's safer
[10:23] <dimitern> voidspace, cheers
[10:29] <voidspace> dimitern: oooh, conflicts
[10:29] <voidspace> fun
[10:29] <voidspace> only 3 files, one of which is dependencies.tsv
[10:31] <dimitern> voidspace, only 3 files with conflicts? That's not too bad :)
[10:31] <voidspace> hah
[10:31] <voidspace> I guess so
[10:32] <dooferlad> voidspace: master --> feature branch should be done as a "merge commit", which is what "git merge master feature-branch-name" does. https://www.atlassian.com/git/tutorials/merging-vs-rebasing/conceptual-overview seems to be a good doc on the subject that I need to read.
[10:33] <voidspace> dooferlad: well, all I *can* do is propose a branch for the bot to land
[10:34] <voidspace> dooferlad: anything else will require frobware
[10:34] <voidspace> hmmm
[10:35] <voidspace> dooferlad: if I'm *on* the feature branch - isn't that command the equivalent of "git merge upstream/master"
[10:35] <dooferlad> voidspace: yes
[10:35] <voidspace> good, thanks
[10:35] <voidspace> that's what I've done
[10:41] <frobware> voidspace, I'm back. 1:1 now?
[10:42] <voidspace> frobware: hey, hi
[10:42] <voidspace> frobware: happy new year
[10:42] <voidspace> frobware: gimme 5 to get coffee
[10:42] <frobware> voidspace, sure. HNY
[10:43] <frobware> jam: ping & Happy New Year. Want to catch up later today?
[11:02] <voidspace> frobware: you still there?
[11:02] <voidspace> frobware: you left the hangout
[11:03] <perrito666> morning all
[11:11] <voidspace> dimitern: frobware suggests that as we have the demo coming up it may be better *not* to merge master unless there's anything we specifically need
[11:11] <voidspace> dimitern: frobware thinks it's just adding potential breakage
[11:13] <dimitern> voidspace, frobware, I agree - we can do it after next week
[11:13] <dimitern> frobware, perrito666, morning btw :)
[11:13] <frobware> dimitern, morning
[11:30] <frobware> dimitern, let's use the standup HO
[11:32] <dimitern> frobware, sure, omw
[11:41] <frobware> dimitern, don't think the HO issue is at my end as I was just talking with voidspace
[11:44] <dimitern> frobware, let's try again?
[11:44] <frobware> dimitern, OK
[11:45] <mup> Bug #1530840 opened: juju status-history too noisy with update-status <kanban-cross-team> <landscape> <juju-core:New> <https://launchpad.net/bugs/1530840>
[11:51] <dimitern> frobware, one last try? :)
[11:57] <mup> Bug #1530840 changed: juju status-history too noisy with update-status <landscape> <juju-core:New> <https://launchpad.net/bugs/1530840>
[12:00] <mup> Bug #1530840 opened: juju status-history too noisy with update-status <landscape> <juju-core:New> <https://launchpad.net/bugs/1530840>
[12:15] <dimitern> dooferlad, thanks for the review!
[12:26]  * fwereade is in london; is rapidly becoming overwhelmed with passport things and bank things and other tedium; is likely to be gone for much of today and weds and fri; marking self out on calendar; but ping me if you need me and you might be lucky
[12:28] <dimitern> fwereade, safe travels :)
[12:32] <fwereade> dimitern, cheers :)
[14:04] <frobware> dimitern, ping. my ISP issues have gone away
[14:04] <frobware> dimitern, can we sync?
[14:05] <dimitern> frobware, sure, let's
[14:06] <dimitern> frobware, I'm in the standup HO
[14:50] <cherylj> frobware: you around today?
[14:50] <frobware> cherylj, Happy New Year!
[14:50] <cherylj> frobware: thanks, you too!
[14:51] <cherylj> frobware, jam, did a unit test get written for http://reviews.vapour.ws/r/3436/ ?
[14:52] <frobware> cherylj, I haven't caught up with jam today but I was going to add a unit test today, then we can review and consider for merging. ok?
[14:52] <cherylj> frobware: sounds good.  Thanks!
[14:53] <frobware> cherylj, I need to catch up with dooferlad first though...
[14:53] <cherylj> k
[14:53] <frobware> dooferlad, HNY && can we sync for 15 mins?
[14:54] <dooferlad> frobware: give me 5 mins - doing some network configuration
[14:54] <frobware> dooferlad, ack
[14:55] <frobware> dooferlad, sounds like my (ISPs) morning. :)
[15:02] <dooferlad> frobware: ok, ready.
[15:04] <dooferlad> frobware: I am lurking in https://plus.google.com/hangouts/_/canonical.com/juju-sapphire
[15:05] <perrito666> mgz:  ping
[15:07] <ericsnow> katco: standup?
[15:08] <frobware> dooferlad, omw
[15:12] <mgz> perrito666: yo
[15:13] <perrito666> have moment for a priv chat?
[15:18] <mgz> perrito666: for you...
[15:38] <natefinch> cherylj: what bugs are we supposed to be working on for bug squad?
[15:38] <cherylj> natefinch: I'm working on that list now
[15:39] <rick_h_> cherylj: also please check with alexisb/mramm on some issues the qa folks have getting tests going on the controller branch as potentials please
[15:40] <cherylj> rick_h_: will do
[15:40] <rick_h_> cherylj: as we should treat those as 2.0 alpha blockers atm based on some small irc conversations
[15:41] <cherylj> rick_h_: sounds good.  jog, sinzui,  abentley, do you have bug #s for stuff blocking controller rename branch testing?
[15:42] <sinzui> cherylj: I was just asking the same question. I expect to know shortly
[15:42] <cherylj> k, thanks!
[15:45] <abentley> cherylj: Here are the bugs marked as affecting controller-rename: https://bugs.launchpad.net/juju-core/controller-rename/
[15:46] <cherylj> thanks, abentley
[15:48] <frobware> voidspace, please could you take a look over dimitern's PR as we want to land this soon-ish for the demo. thx. http://reviews.vapour.ws/r/3448/
[16:06] <voidspace> frobware: ok
[16:06] <frobware> voidspace, thx
[16:06] <voidspace> it's kind of huge...
[16:08] <voidspace> dimitern: I'm worried about params.Address having a SpaceName added, does this mean that all APIs returning or taking an address should be version bumped?
[16:40] <natefinch> cherylj: bug fixes for 2.0 should still be on master, I assume?
[16:41] <voidspace> dimitern: frobware: reviewed, with several questions/comments
[16:41] <cherylj> natefinch: yes
[16:41] <natefinch> cherylj: cool thanks
[16:48] <frobware> dimitern, do you have some time after the network call to talk about the unit test case for the DNS issue?
[16:49] <dimitern> frobware, ok, sure
[16:49] <dimitern> voidspace, thanks!
[16:57] <jam> frobware: hey, I did intend to meet with you today, it looks like my IRC client didn't actually connect properly today. I got your message from hours ago just recently
[16:59] <frobware> jam: I futzed around with what turned out to be an ISP throttling issue so it may be related.
[17:07] <cherylj> frobware, dimitern can you ping me when you're free.  We need to talk about another potential blocker for 1.25.2
[17:44] <frobware> cherylj, I'm around
[17:45] <cherylj> frobware, sinzui, mgz, jog:  https://plus.google.com/hangouts/_/canonical.com/cheryl-jennings?authuser=0
[17:46] <mgz> you named the hangout after yourself?
[17:46] <mgz> are you the topic? :P
[17:47] <cherylj> mgz: you should wait until I leave, then you can talk about me
[19:22] <mup> Bug #1530957 opened: New EC2 Korea region <juju-core:New> <https://launchpad.net/bugs/1530957>
[20:05] <natefinch> perrito666: can you review me? http://reviews.vapour.ws/r/3452/
[20:05] <perrito666> well not you, but certainly your code
[20:07] <natefinch> heh
[20:07] <natefinch> thx
[20:08] <perrito666> ship it
[21:31] <mup> Bug #1530992 opened: Can't remove machine from Juju <juju-core:New> <https://launchpad.net/bugs/1530992>
[21:34] <mup> Bug #1530992 changed: Can't remove machine from Juju <juju-core:New> <https://launchpad.net/bugs/1530992>
[21:43] <mup> Bug #1530992 opened: Can't remove machine from Juju <juju-core:New> <https://launchpad.net/bugs/1530992>
[22:08] <perrito666> wallyworld: awake so early?
[22:08] <wallyworld> been up for a while :-)
[22:08] <perrito666> good to see you are trying that not overwork thing....
[22:10] <perrito666> is standup happening today?
[22:10] <wallyworld> yep
[22:11] <perrito666> good, I had to nurse my google calendar back into health after all that shaking near december
[22:23] <cherylj> Hey axw, did you see bug 1527681?
[22:23] <mup> Bug #1527681: azure provider does not appear to be opening ports <juju-core:Triaged> <https://launchpad.net/bugs/1527681>
[22:27] <axw> cherylj: no, I did not. will take a look later on
[22:27] <cherylj> thanks, axw
[22:29] <perrito666> axw: you are up too? what is it with you people and getting up so early?
[22:29] <axw> perrito666: I wouldn't normally, had to administer antibiotics
[22:30] <axw> perrito666: house full of chest- and ear- infected people
[22:31] <perrito666> axw: well that is what you get for getting vacation advice from wallyworld
[22:37] <perrito666> axw: wallyworld says the calendar that anastasia is off, would you guys like to call now? (also it would help me finish my day :p)
[22:38] <wallyworld> perrito666: sorry, in another meeting
[22:58] <cherylj> jog: did you guys get a chance to test the destroy-environment --force with 1.8.2?
[22:58] <cherylj> and checking for leaked container IPs?
[23:00] <cherylj> jog, mgz, I also attempted to deploy containers with frobware's DNS patch on 1.8.2, and saw that it didn't fix the issue
[23:00] <cherylj> but it worked on 1.9
[23:02] <mgz> cherylj: aha
[23:03] <cherylj> yeah.  Awesome :(
[23:05] <jog> mgz, did you start a new run of something?
[23:06] <mgz> jog: yup, see ^, I rebuilt the feature branch with the fix so we had a current run on that
[23:06] <mgz> given current info it should just be exatly the same
[23:07] <mgz> wait, < then ^, different channel
[23:08] <cherylj> ah, I'm not on 1.8.2.  I'm on 1.8.3+bzr4053-0ubuntu1.
[23:08] <cherylj> not that it'll make too much difference, maybe
[23:08] <jog> mgz, I had re-run 3430. Containers get past pending with that older build but this new run started before I was able to snapshot the leases file.
[23:09] <mgz> hm, the problem with the --keep-env thing on short timeout
[23:10] <cherylj> jog, mgz, I'm wondering if this is a bug with MAAS?    I see that a device gets created for the container, and that the device is removed (or at least doesn't show up on the devices list in the dashboard)
[23:10] <cherylj> but I don't see a release of the IP
[23:11] <cherylj> let me try it with 1.9 and see if there's a difference.
[23:14] <mgz> well, the point is we were not previously exercsing this maas 1.8 networking code at all previously
[23:15] <mgz> so, even if it's maas not working as api promises, it's our problem because the change is juju using those apis where we didn't before
[23:17] <wallyworld> perrito666: standup?
[23:17] <perrito666> going
[23:27] <jog> mgz, I'll going to try a maas-1_8-deployer run with Juju 1.25.0... do you have anything you plan to kick off?
[23:29] <mgz> jog, nope, but be aware the current queue isn't empty
[23:29] <jog> yeah, I see that now