axwabentley: don't suppose you're working? CI seems to have died... merge job has been running for 2 hours01:10
axwI'll just kill it and hope for the best01:11
* thumper heading out for a bit, taking daughter to BJJ02:14
=== natefinch-afk is now known as natefinch
natefinchgoogle: ps human readable memory03:40
natefinchresponse: <hugeass command>03:40
natefinchnobody's put a -h on ps, huh?03:41
=== Makyo is now known as Guest78890
=== meetingology` is now known as meetingology
=== JoseeAntonioR is now known as jose
natefinchnobody's put a -h on ps, huh?05:42
natefinchoops wrong window05:42
natefinchoops wrong window05:52
mupBug #1516891 opened: juju 1.25 misconfigures juju-br0 when using MAAS 1.9 bonded interface <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1516891>06:31
mupBug #1516891 changed: juju 1.25 misconfigures juju-br0 when using MAAS 1.9 bonded interface <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1516891>06:34
mupBug #1516891 opened: juju 1.25 misconfigures juju-br0 when using MAAS 1.9 bonded interface <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1516891>06:43
=== mup_ is now known as mup
frobwaredimitern, ping 1:1?09:04
dimiternfrobware, sorry, omw09:05
axwwallyworld: http://reports.vapour.ws/releases/3318  -- azure-arm-provider is blessed. what's the process to merge into master?09:54
wallyworldaxw: yay. when master unblocked, just create a branch, merge in tip of feature branch, and propose09:54
axwwallyworld: cool. no need for review on that I take it?09:55
wallyworldaxw: judgement call, usually no09:55
dimiternvoidspace, frobware, jam, fwereade, standup?10:01
voidspacedimitern: bugger, bugger, bugger10:14
voidspacegot distracted by work10:14
voidspacedimitern: frobware: dooferlad:  I guess you've finished10:15
dooferladvoidspace: yep10:15
voidspacedimitern: frobware: dooferlad: my standup then - I made the changes to add a machine.Principals method for my "address picking algorithm change"10:16
dimiternvoidspace, :) hey, you didn't miss much10:16
voidspacedimitern: frobware: dooferlad: that made tests pass on CI - it's landed on 1.25 but master is still blocked10:16
dimiternvoidspace, nice! yeah - too bad for master :/ I have 3 PRs blocked as well10:16
voidspaceI thought I'd finished the implementation of Subnets using the new MAAS API and am waiting on the test harness - will need to sync up with dooferlad for that10:17
voidspaceso I'd started on the ListSpaces implementation10:17
dimiternvoidspace, please, call it Spaces()10:17
voidspacein the process of that this morning I discovered a flaw in the new Subnets code (wasn't filtering by subnet ID)10:17
voidspacedimitern: ok - I thought ListSpaces was your idea10:17
voidspacebut fine10:17
dimiternvoidspace, it was an early idea, but since we have Subnets() now, let's keep the consistency in names10:17
voidspaceand it was fixing the subnet ID filtering that distracted me10:18
voidspacedone now10:18
voidspacedooferlad: have you made a start on the maas test server update?10:18
dooferladvoidspace: yes10:18
dimiternvoidspace, cheers10:19
dooferladvoidspace: working on it now. Will ping you when I have something worth sharing10:19
voidspacedooferlad: cool, let me know if you have any questions10:19
voidspacedooferlad: great!10:19
voidspacedooferlad: I'll carry on with Spaces then - can land it as a single branch10:19
voidspacedimitern: environ.Spaces() can just return a map of string -> []SubnetInfo - right?10:23
voidspacedimitern: and should we do anything with the maas "Default Space" (named like that)10:23
voidspacedimitern: we want to make sure our default space is the same as the maas default space10:23
voidspaceotherwise nothing works10:24
dimiternvoidspace, I think Spaces() needs to return []network.SpaceInfo10:26
voidspacedimitern: ok10:27
voidspacedimitern: all SpaceInfo will have is a name and a []SubnetInfo10:27
dimiternvoidspace, and that in turn should have a Name, ProviderId, Subnets []network.Id10:27
voidspacethere's no provider id beyond name10:27
voidspacedimitern: you want network.Id for subnets rather than SubnetInfo ?10:27
dimiternvoidspace, I don't think we should care about the "Default space"10:27
voidspacedimitern: what do you mean by "not care" - not include it?10:28
dimiternvoidspace, well, if we require Spaces() to return the full subnets info, wouldn't that be too restrictive on providers?10:28
dimiternvoidspace, no, include it - we just won't use it for openstack10:28
voidspacethe only provider we have that can list spaces is maas10:28
dimiternvoidspace, for now10:28
voidspaceand I suspect that for any provider we implement spaces for, the only way we'll get a slice of subnet IDs is by getting full subnet info anyway10:29
dimiternvoidspace, will it be easier to do []SubnetInfo instead?10:29
dimiternvoidspace, I mean, SpaceInfo with Subnets []SubnetInfo10:29
voidspaceit would mean throwing away less information away10:29
voidspaceso marginally less work10:29
dimiternvoidspace, ok, let's do it so Spaces() return the full subnets info10:30
voidspaceand include default space10:30
voidspacewe need to be careful when we populate the model that we don't end up with a "juju default space" and a "maas default space" that are actually the same thing but we treat them differently10:31
dimiternvoidspace, well, since a juju space name cannot contain a space, "Default space" will be the ProviderId, the juju name will need to be something like "default-space" I guess10:33
voidspacedimitern: so I need to transform all maas names into juju compatible ones10:33
voidspacedimitern: so ironically the "Provider Id" will be much more human readable than the "Space Name"10:34
voidspacedimitern: why do we have that restriction?10:34
dimiternvoidspace, because of constraints and bindings10:34
voidspacefair enough10:34
dimiternvoidspace, the transformation should be just lowercase it and replace spaces with -10:35
voidspacedimitern: sooo... when I fetch the space name from the maas subnet result I need to transform there too10:35
voidspaceSubnetInfo.SpaceName has to be the juju space name10:35
dimiternvoidspace, yeah I think so10:36
voidspacedimitern: thanks10:37
voidspacedimitern: hmmm... that's a one way transform though10:37
voidspacedimitern: (i.e. you won't be able to deterministacally go from the SpaceName on a Subnet to the MAAS space)10:38
voidspacedimitern: you can list spaces to see that though10:38
voidspacewhich will have both10:38
voidspaceprobably doesn't matter10:38
dimiternvoidspace, when talking to maas we always need to use the provider id - we should have it once the space is imported10:38
voidspacedimitern: sure10:39
voidspacedimitern: but if someone sees a SubnetInfo (i.e. output from subnets list) the space name shown there is *not* the maas space name10:39
dimiternvoidspace, but I don't think we'll need to do juju space name -> maas space provider id anywhere10:39
voidspaceI'm talking about the user - not us10:39
dimiternvoidspace, ah, sure - we need to have ProviderSpaceId on SubnetInfo10:39
dimiternvoidspace, in addition to SpaceName10:40
voidspacethat means a new facade10:40
voidspaceas it's a change to the api output10:40
voidspaceare you *sure* we need that as it's a lot of extra work10:40
voidspace(well - a moderate amount)10:40
dimiternvoidspace, ProviderSpaceId is optional10:40
voidspaceI say we should be aware of it but not do it for now10:40
dimiternvoidspace, but good point about the versioning10:41
voidspacedimitern: still need a new facade, if someone writes any code depending on that value being present then they need to know which api version to require10:41
dimiternvoidspace, that's the client subnets facade you're talking about?10:41
voidspacedimitern: yep10:41
voidspaceas it's in 1.2510:41
dimiternvoidspace, yeah, I think before the release we should bump the version for sure10:41
voidspacedimitern: I say we don't need SpaceProviderId on SubnetInfo yet10:42
dimiternvoidspace, but for the time being let's just keep it in mind (probably add a card for it though, once your change lands)10:42
voidspacenobody may actually care in practise, but if they do we can add it10:42
dimiternvoidspace, we should be serious about api backwards compatibility10:43
dimiternvoidspace, but given the time frame, it can wait for a while10:43
voidspacedimitern: so I think I do need to add SpaceProviderId to SubnetInfo - as it's needed for Spaces10:52
voidspacedimitern: however I don't need to add it to the apiserver SubnetResults10:52
dimiternvoidspace, not yet, yep10:53
dimiternvoidspace, it can stay within the provider code10:53
dimiternvoidspace, and for importing at bootstrap we don't need to modify the api facades at all, since we have access to state at that point10:53
voidspacedimitern: and access to the provider10:54
voidspacedimitern: but we do need the proper provider id, so it will need to be on SubnetInfo (which is what we build the state model from)10:55
dimiternvoidspace, we do have access to the provider when we have the environ config10:56
dimiternvoidspace, network.SubnetInfo != params.SubnetInfo btw exactly for that reason10:56
voidspaceyep, understood10:57
mupBug #1516975 opened: Incompatible version formats <juju-core:New> <https://launchpad.net/bugs/1516975>11:02
mupBug #1516975 changed: Incompatible version formats <juju-core:New> <https://launchpad.net/bugs/1516975>11:11
mupBug #1516977 opened: juju upgrade-juju should guess version number <juju-core:New> <https://launchpad.net/bugs/1516977>11:14
mupBug #1516977 changed: juju upgrade-juju should guess version number <juju-core:New> <https://launchpad.net/bugs/1516977>11:26
mupBug #1516975 opened: Incompatible version formats <juju-core:New> <https://launchpad.net/bugs/1516975>11:26
mupBug #1516975 changed: Incompatible version formats <juju-core:Invalid> <https://launchpad.net/bugs/1516975>11:32
mupBug #1516977 opened: juju upgrade-juju should guess version number <juju-core:New> <https://launchpad.net/bugs/1516977>11:32
mupBug #1516989 opened: juju status <service_name> broken <juju-core:New> <https://launchpad.net/bugs/1516989>11:44
fwereadestraw poll: `type NotifyChan <-chan struct{}`, or `type NotifyChannel <-chan struct{}`13:02
fwereadejam, dimitern, frobware, anyone? ^^13:03
dimiternfrobware, I'd vote for the first one13:08
dimiternsorry :) I meant fwereade  ^^13:08
fwereadedimitern, cheers13:09
frobwaredimitern,  fwereade: for me the latter. :)13:17
frobwarefwereade, speaking it out loud (in my head) I'm talking about a "channel"13:18
dimiternfrobware, yeah, but the type name is "chan" and it's more common in the go code base to use Chan vs Channel13:20
fwereadedammit, now it's even again, if someone wants to tie-break?13:22
fwereadeI do favour Chan myself but can't really muster up very strong arguments either way13:23
perrito666I would vote for the seccond, there is no sense in adding the type to the name of something in a typed language13:23
dimiternfwereade, frankly, I don't care that much :) you can count me towards Channel if it helps13:23
fwereadeChannel it is then, thanks all13:24
fwereadeand: dimitern, frobware, perrito666: can I trouble any of you for reviews of http://reviews.vapour.ws/r/3143/ and http://reviews.vapour.ws/r/3146/ please?13:25
fwereadeif I can get LGTMs there I can apply the various fixes for the pipeline to http://reviews.vapour.ws/r/3147/ and land in one fell swoop13:26
dimiternfwereade, I'll have a look shortly13:27
fwereade3143 has already been looked at and I *think* just needs an LGTM and/or second opinion on the open issue13:27
fwereade3146 is just a copy-code-and-fix-imports13:27
fwereadedimitern, tyvm13:27
fwereadefrobware, opinion on thumper's comment at http://reviews.vapour.ws/r/3143/diff/3/?file=159341#file159341line96 ?13:48
fwereadefrobware, am inclined to drop the issue but if anyone can tell me *why* it's bad I will change it13:48
frobwarefwereade, looking13:50
frobwarefwereade, plan.Init is actively populated with workers at this stage?13:54
fwereadefrobware, yeah13:55
fwereadefrobware, ha! some asshole could change Init once the func's returned13:55
fwereadefrobware, thanks13:55
dooferladdimitern, frobware, voidspace: https://plus.google.com/hangouts/_/canonical.com/maas-juju-net14:02
dimiterndooferlad, omw 2m14:02
mupBug #1516975 opened: Incompatible version formats <juju-core:New> <https://launchpad.net/bugs/1516975>14:09
voidspacedooferlad: sooo...14:46
dooferladvoidspace: yep?14:46
voidspacedooferlad: I'll be changing my implementation to call the /node/{id}/ endpoint which now includes subnet information in the output14:46
voidspacedooferlad: which the test server may or may not already support - probably not14:47
dooferladno, not yet14:47
voidspacedooferlad: so if you could include that in your test server work that would be wonderful :-)14:47
dooferladvoidspace: sure14:47
natefinchrofl.... the output for juju run is sorted by machineID... alphabetically... i.e. 1, 10, 11, 12, 2, 3, 414:56
mattywkatco, not merging lxd in master? I'm excited for it to happen though15:07
mupBug #1517076 opened: juju run output is sorted by machine id alphabetically not numerically <juju-core:New> <https://launchpad.net/bugs/1517076>15:15
dooferladvoidspace: this is more involved than just subnets because they depend on fabrics and VLANs. Fun :-|15:16
voidspacedooferlad: we're not initially going to be using fabrics and vlans though15:16
voidspacedooferlad: so even if they *should* appear in json output you can restrict the test server to just stuff that we're using15:16
voidspacewhen we need fabrics and vlans we can add them15:17
dooferladvoidspace: hmm, OK15:17
voidspacetest server support doesn't need to be complete15:17
dooferladvoidspace: I will just dump out some sensible defaults15:17
voidspaceit doesn't look like I'll need to query a subnet's ip addresses by the way15:17
voidspaceif you haven't done that yet15:17
voidspaceif you have there's no harm in keeping it15:17
dooferladvoidspace: Oh, I haven't got the basics down yet, but ignoring VLANs removes quite a chunk of work.15:18
voidspaceyay \o/15:18
dimiternfwereade, sorry, I just finished a call now and managed to push first of your reviews15:23
fwereadedimitern, np, I've been tussling with worker/environ again15:23
katcomattyw: we're merging lxd into master. waiting for bless from ci15:27
fwereadedimitern, and, thanks for the detailed review: I'm not sure I'll be making any code changes there, but there's no harm in making the comments less stupid15:27
dimiternfwereade, and the other one is done - I hope the reviews are useful  :)15:28
dimiternfwereade, yep +115:28
dimiternkatco, hey, any idea about that blocker bug? didn't we decide to rollback issues like that..15:29
katcodimitern: we're going to try and get a fix in before EOD today, if not we'll revert15:31
mattywkatco, much excite ;)15:35
katcomattyw: :)15:35
dimiternkatco, ok, thumbs up then :)15:38
mupBug #1517092 opened: [xenial] libgo panic doing a bootstrap on ARM64 <arm64> <bootstrap> <xenial> <juju-core:New> <https://launchpad.net/bugs/1517092>15:45
mupBug #1517092 changed: [xenial] libgo panic doing a bootstrap on ARM64 <arm64> <bootstrap> <xenial> <juju-core:New> <https://launchpad.net/bugs/1517092>15:48
mupBug #1517092 opened: [xenial] libgo panic doing a bootstrap on ARM64 <arm64> <bootstrap> <xenial> <juju-core:New> <https://launchpad.net/bugs/1517092>15:54
voidspacedimitern: frobware: dooferlad: openstack hangout?16:33
dooferladvoidspace: we are skipping today I think16:34
voidspacedooferlad: no0pe16:34
voidspacedooferlad: we skipped the second one last week16:34
dooferladvoidspace: and at this mornings hangout we discussed canceling this one16:35
dooferladvoidspace: which I realise you weren't at16:35
dooferladvoidspace: so, we should have mentioned that! I guess it should have been canceled in our calendars as well. frobware, dimitern?16:36
voidspacedooferlad: dimitern and the open stack guys are here16:36
voidspacebut it's a low key discussion16:36
voidspacedooferlad: probably no harm in you skipping16:37
natefinchif we juju add-machine and then juju deploy, shouldn't the deployed unit get placed on the existing clean machine?16:45
natefinchi.e. instead of having deploy add another machine16:45
natefinchfwereade: ^16:45
dooferladvoidspace: https://code.launchpad.net/~dooferlad/gomaasapi/subnets16:50
dooferladvoidspace: I can remove most of the VLAN code (untested) and propose a merge now, or you can just use what is there until I have finished up vlans, spaces and subnets. Shouldn't take long now.16:51
voidspacedooferlad: I can start using what you've got16:52
voidspacedooferlad: I'm "retooling" to use the node api instead of subnets plus addresses for when we're filtering by node id16:53
voidspacedooferlad: that's almost done and I have the start of maasEnviron.Spaces() too16:53
voidspacedooferlad: so plenty to be getting on with, but I'll need this code "real-soon-now"16:53
voidspacedooferlad: if I need it before you're done I'll use your branch until it lands16:53
dooferladvoidspace: sounds good. So far I just have basic get/post/put/delete support for subnets. I need to integrate subnets into nodes, add op=?? (if you need that) etc.16:55
voidspaceI don't need ip_addresses now16:55
voidspaceI still need unreserved_ranges16:56
cheryljsinzui: for the 1.26-alpha2 release notes, should they just be appended to the 1.26.0 release notes doc?17:11
sinzuicherylj: yes please17:11
cheryljsinzui: thanks!17:11
fwereadenatefinch, assuming constraints match hardware characteristics, yes17:12
natefinchfwereade: was not seeing that happen last night on 1.2517:13
fwereadenatefinch, I don't think I have the mental bandwidth to do more than say "that sounds like a bug then"17:14
natefinchfwereade: no problem, just wanted to confirm that it really should be putting the unit on the existing machine, assuming the machine would otherwise be ok.17:15
natefinch(clean, matches constraints, etc)17:15
=== akhavr1 is now known as akhavr
marcoceppicherylj: we're back to power818:09
marcoceppiit's no longer a proxy issue18:09
marcoceppiwe're getting a machine-0 log in the next 30 mins18:09
=== mbarnett` is now known as mbarnett
katconatefinch: how's bug fix coming?19:37
natefinchkatco: having some trouble reproing... running CI test s manually now to see if I can see it happen19:39
katconatefinch: k, lmk what happens. maybe menn0 did fix it :)19:39
natefinchthat would be cool :)19:40
natefinchmgz: you around?20:06
natefinchor abentley?20:06
abentleynatefinch: Hi.20:07
natefinchI'm looking at the jes CI failure on master... but when I try to run it I get provider validation failed: invalid EC2 provider config: environment has no access-key or secret-key20:07
natefinchthis is when it's trying to do create-environment on top of the controller environment20:08
natefinch...obviously the controller environment was created fine with an access key and secret key20:08
abentleynatefinch: I could be wrong, but I don't think the controller environment provider config is used to create the hosted environments.20:12
natefinchthumper, menn0: is there a trick to getting the jes CI test to run?  It seems to be failing when it tries to create-environment on top of the controller environment, saying it can't find EC2 keys20:13
thumpernatefinch: you need to give it config for the environment, which includes cloud credentials20:13
abentleynatefinch: Which jes test do you mean?20:14
natefinchthumper: I did... it bootstraps the controller environment just fine, then fails to create the child environment (or whatever we're calling them)20:15
natefinchabentley: assess_jes_deploy20:15
thumperdid you pass the config through to the create environment call?20:16
natefinchthumper: I don't know?  I gave the script the CLI args it asked for, and it didn't say I was missing any20:17
thumperhosted environments are what we are calling them20:17
abentleynatefinch: Does environments.yaml contain  access-key and secret-key for the "env" you specified?20:18
natefinchabentley: yes. Like I said, it was able to bootstrap the controller environment, so obviously those exist and are correct (also I can bootstrap that environment manually).20:20
menn0natefinch: assess_jes_deploy worked for me but I had to hack it a little to do an --upload-tools so it would use juju from my machine20:21
* menn0 checks what he did20:21
thumpernatefinch: I'm not sure how the ci script creates the hosted environment20:21
abentleynatefinch: Not obviously.  Perhaps bootstrap respects environment variables and create-environment does not, for example.20:21
menn0abentley, natefinch: I don't have any EC2 related env vars set20:23
menn0abentley, natefinch: here's what I did: ./assess_jes_deploy.py menn0-ec2 ~/tmp/workspace/bin/juju ~/tmp/workspace/logs menn0-testing20:23
menn0menn0-ec2 is an EC2 env defined in my environments.yaml20:24
menn0menn0-testing is the name of an env that the test will create, cloning the settings from menn0-ec220:24
menn0~/tmp/workspace/bin/juju is the path to the juju binary (jujud etc are next to it in the same directory)20:25
natefinchmenn0: that's what I did, too20:25
menn0~/tmp/workspace/logs is where I asked for the artifacts to go20:25
menn0natefinch: I also modified assess_jes_deploy.py so that the uploadTools arg to boot_context() is True instead of False20:27
menn0but I don't think that will cause the problem you're seeing20:27
menn0natefinch: maybe check your env for EC2 variables? Maybe there's some set that are causing a problem.20:27
menn0natefinch: try "set | grep -e AWS -e EC2"20:29
natefinchhmm, so I do have the AWS keys in my environment20:29
natefinchmaybe that's the problem20:29
menn0natefinch: yep, try removing them20:29
natefinchor rather, lack of them in the environments.yaml20:32
menn0natefinch: that makes even more sense20:41
menn0I imagine the AWS keys will need to be in environments.yaml in order for create-environment to work20:42
natefinchgah, now it's giving me "failed to create new environment: admin-secret should never be written to the state"  sigh20:46
thumpernatefinch: I bet the config from environments.yaml is just being copied, try not explicitly setting admin-secret in the environments.yaml21:02
thumperactually, create-environment should read the environment vars21:02
natefinchthumper: maybe the script is stripping out the env vars?21:04
* natefinch shrugs21:04
natefinchI can try doing it manually when the script is finished (this is a long-ass test)21:04
* thumper shrugs21:04
natefinchahh, wondrous exceptions21:06
natefinchOSError: [Errno 17] File exists: '../logs/machine-0'21:06
perrito666tautological errors, next one should be file is file21:07
natefinchlol, I think the CI test failed while trying to dump logs21:14
natefinchthanks, exceptions!21:14
thumperquiet expectations21:14
natefinchso after 15 minutes of running the test... it fails because the directory it was trying to create... existed.  Sigh21:17
menn0natefinch: I wonder if mgz's changes to grab logs for each environment is trying to write all the logs into the same place21:18
natefinchhmm could be, though it was trying to create machine-0 ... do we have a machine-0 in the host environment?21:18
perrito666yes, that is a very annoying characteristic of CI tests, they assume a pristine env21:22
mgzmenn0: I did not commit my change yet21:27
mgzCI tends to just be unforgiving about expected start state21:28
menn0mgz: ah right21:28
menn0so it's just that natefinch needs to clear the artifacts directory. there's probably stuff from a previous attempt hanging around.21:28
mgzI need to restart for hangouts, brb21:30
natefinchthanks, retrying with empty logs dir21:35
natefinchum hmm.. weird... cannot run instances: Your quota allows for 0 more running instance(s). You requested at least 1 (InstanceLimitExceeded)21:52
wallyworldmenn0: do we still need to use st.docID(localid) when creating a doc to insert into a collection, or is the prefixing of the doc id with env-uuid automatic now?21:53
wallyworldeverything in state still seems to use st.docID()21:53
menn0wallyworld: it's not necessary any more21:54
wallyworldawedome, ty21:54
menn0wallyworld: we can remove all the calls21:54
menn0wallyworld: I've got a tech debt card for that21:54
wallyworldyay, ok21:54
natefinchkatco: I'm not going to be able to figure out this bug before dinner. I have time after dinner, but I've just been strugging with CI too much21:54
menn0but you know how it is21:54
katconatefinch: ok, i'll discuss in the release meeting. can you log where you're at somewhere21:55
katconatefinch: that i can look at?21:55
katcoaxw: wallyworld: does the new azure provider use simplestreams?21:56
wallyworldkatco: no21:56
wallyworldit queries the cloud directly21:56
katcoalexisb: ^^21:56
wallyworldto look up images ids21:56
katcowallyworld: ty21:56
wallyworldkatco: i already told alexisb  taht21:56
natefinchkatco: not a lot to say.  Couldn't repro manually, CI hasn't gotten through the test yet (each attempt is like 20 minutes)21:59
natefinchkatco: updated the bug: https://bugs.launchpad.net/juju-core/+bug/151614421:59
mupBug #1516144: Cannot deploy charms in jes envs <blocker> <charms> <ci> <regression> <juju-core:Fix Committed by menno.smits> <https://launchpad.net/bugs/1516144>21:59
=== natefinch is now known as natefinch-afk
katconatefinch: ok21:59
katcowwitzel3: ericsnow_: any updates on your end?22:20
menn0thumper: review pls: http://reviews.vapour.ws/r/3169/22:21
* thumper looks22:21
ericsnow_katco: patch should be done in the next little while (based on Nate's patch + tests)22:22
katcoericsnow_: cool. demonstrably addresses memory issue?22:22
ericsnow_katco: yes22:22
perrito666super, a bit of rain and power starts doing funny stuff22:26
menn0thumper: thanks22:28
sinzuikatco: cherylj : Do you have time to review http://reviews.vapour.ws/r/3170/22:47
wwitzel3katco: not yet, I'll be working on it tonight to try and at least get past this stupid series issue.22:56
katcowwitzel3: ok22:56
wwitzel3katco: my plan was to bug someone who is starting their day to take a look at ti with me22:56
katcowwitzel3: not a bad idea. alexis is also going to see if jam or fwereade have any insights22:56
wwitzel3katco: yeah, that'd be great. I was going to bug people after Jessa and I have dinner.22:57
katcowwitzel3: k sounds good. say hi to natefinch-afk; he'll be working on trying to repo the master blocker tonight :p22:58
katcorepro rather22:58
alexisbthumper, wallyworld, ^^^ if someone is around when wwitzel3 is back on it would be nice to have a AUS/NZ timezone person to bounce ideas off of23:07
=== ericsnow_ is now known as ericsnow

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!