[00:00] <bac> hi rick_h_.  otp, but what's up?
[00:01] <rick_h_> fyi, I talked to arosales about quickstart and it's not going anywhere for this cycle
[00:01] <bac> six month cycle?
[00:01] <rick_h_> bac: we'll work on introducing it to the guys on eco some, arosales would like to setup a meet sometime to run them through the basics
[00:01] <rick_h_> bac: but we won't hand anything off until Oct
[00:01] <rick_h_> bac: rgr
[00:01] <bac> rt
[00:01] <rick_h_> 14.10 cycle kind of thing
[00:02] <rick_h_> so we want to get the idea on the table, but not actually move for now. So just a heads up that we can continue our current plans as they are
[00:24] <arosales> rick_h_, bac, I am going to talk to a few guys on my team to check interest in transitioning. I'll get back to you guys once I have done so, and perhaps we an do some knowledge transfer
[00:26] <arosales> bac, rick_h_ apologies we won't be able to dedicate time to dev on it this cycle. Perhaps some items will move faster than we think (I guess that happens sometimes right :-)
[06:14] <kadams54> huwshimi: you around?
[06:15] <huwshimi> kadams54: Hey!
[06:16] <kadams54> I ran into a potential bug earlier today and Jeff said you might be working on a fix…
[06:17] <kadams54> Here's how to reproduce on comingsoon.jujucharms.com:
[06:18] <kadams54>  1) Deploy the Mediawiki bundle, then drag-n-drop a second mysql charm. It also gets the name "mysql" which means it will fail when you try to deploy it.
[06:18] <kadams54> But if you try to rename it, there isn't a button anymore to save the changes to the ghosted charm's config.
[06:19] <kadams54> If there's a fix in progress for that, great. If not, I'll create a bug report.
[06:19] <huwshimi> kadams54: Oh yeah, I'm not working on a fix, but we discussed in a call this morning and Rick said that the inspector needs be updated to auto-save those config changes.
[06:20] <huwshimi> kadams54: There are some broader changes on the ghost inspector, maybe it'll be done as part of that.
[06:20] <kadams54> Ah, excellent.
[06:20] <huwshimi> kadams54: I guess a bug report at this stage would be prudent.
[06:20] <kadams54> Yeah, will do.
[06:20] <kadams54> Don't want to lose visibility
[06:21] <huwshimi> kadams54: Just so we don't release mv without fixing it.
[06:21] <huwshimi> yeah
[06:21] <huwshimi> Thanks
[06:21] <huwshimi> kadams54: But yes, that is my fault :)
[06:22] <kadams54> Meh, we all knew the button in the inspector was going away.
[06:26] <kadams54> Alright, with that, I'm off to bed :-)
[06:27] <kadams54> Have a good rest of the day!
[07:17] <rogpeppe> mornin' all
[07:21] <huwshimi> Morning
[08:21] <frankban> morning rogpeppe: I'll start migrating filetesting to github.com/juju/testing/filetesting
[08:21] <rogpeppe> frankban: cool.
[08:21] <rogpeppe> frankban: i could work concurrently on other related stuff if you feel it would speed things up
[08:25] <frankban> rogpeppe: sure, I guess the next thing is handling juju/osenv, e.g. decoupling utils from juju/osenv
[08:26] <frankban> rogpeppe: the goal is to have a github.com/juju/utils project
[08:26] <rogpeppe> frankban: a lot of osenv looks quite core-specific
[08:27] <rogpeppe> frankban: the only thing that isn't is the proxy stuff, i think
[08:29] <frankban> rogpeppe: ok, so I guess it makes sense to have utils/zip and utils/set outside juju-core
[08:31] <frankban> rogpeppe: charm depends on both, and also on utils itself, but AFAICT only for stuff like ReadSHA256, ReadFileSHA256 and ReplaceFile. Perhaps a good path is to move juju-core unrelated stuff to github and change charm to only depend on the github project
[08:31] <rogpeppe> frankban: i think there are (at least) two splits that should happen
[08:32] <rogpeppe> frankban: utils/osenv should split out the juju home stuff
[08:32] <rogpeppe> frankban: (or perhaps split out the proxy stuff)
[08:33] <rogpeppe> frankban: and utils itself should be split into coherent packages containing related functionality, rather than being a grab-bag of stuff
[08:34] <rogpeppe> frankban: i'll try and come up with a coherent scheme for that
[08:35] <frankban> rogpeppe: great, thanks
[08:55] <frankban> rogpeppe: uhm, it seems juju is not using the latest revision of github.com/juju/testing. this is the missing change: https://github.com/juju/testing/commit/83bf0cdc931b7556c93e8d496978b3f010d50ab5 . Do you think it's safe to include that? 
[08:56] <rogpeppe> frankban: yeah, i do
[08:56] <frankban> cool
[08:57] <rogpeppe> frankban: i'd propose a CL with a single change to the dependencies.tsv file to update that
[08:57] <frankban> rogpeppe: yeah, that's what I was thinking
[08:58] <frankban> rogpeppe: ah, feel free to create a kanban card in Project A for what you are working on
[09:36] <frankban> rogpeppe: I need a review for https://codereview.appspot.com/100740044 (trivial)
[09:37] <rogpeppe> frankban: LGTM
[09:37] <frankban> thanks
[09:54] <frankban> rogpeppe: have you ever seen this? fatal: reference is not a tree: a99ca0f5b8d5b7ad608fd7214e8ba3d7b6279f63.
[09:54] <rogpeppe> frankban: i think i might have - was that printed by git?
[09:55] <frankban> I think so, godeps in tarmac reports this error from git I guess
[09:55] <frankban> rogpeppe: do we need to pull from github/juju/testing in tarmac?
[09:56] <rogpeppe> frankban: i *thought* it pulled automatically
[09:58] <rogpeppe> frankban: am asking in juju-core - someone might know
[09:58] <frankban> thanks
[10:06] <frankban> rogpeppe: unrelated: in the process of updating testing, I'd like to go get my fork in a separate GOPATH, and run the tests/verify dependencies. Is it possible to go get a github named branch? I guess no. So maybe this can be done with 1) export GOPATH=... 2) go get github.com/frankban/testing 3) checkout the branch with the updates and 4) go get -u ./...
[10:06] <frankban> correct>
[10:06] <frankban> ?
[10:46] <frankban> rogpeppe: at this point I'd be inclined not to start the filetesting migration, and tackle that on Monday. I can start working on breaking utils/set, what do you think?
[10:47] <rogpeppe> frankban: seems ok to me. i'm currently factoring out apt from utils.
[10:48] <frankban> rogpeppe: so juju-core/utils/set -> juju-core/set, how does it sound?
[10:48] <rogpeppe> frankban: that seems a bit odd to me
[10:48] <rogpeppe> frankban: why move it?
[10:49] <rogpeppe> frankban: i thought it should probably go to github.com/utils/set
[10:49] <rogpeppe> frankban: oops
[10:49] <rogpeppe> frankban: i mean github.com/juju/utils/set
[10:51] <frankban> rogpeppe: IC, right, so 1) we move the juju-core related stuff from utils to their own packages and 2) we migrate utils to github, correct?
[10:51] <rogpeppe> frankban: yeah
[10:51] <rogpeppe> frankban: i don't think we have to migrate all of utils to github - i think juju-core can probably still keep its own utils dir
[10:53] <frankban> rogpeppe: yeah that's reasonable
[11:06] <frankban> rogpeppe: so, after you split apt, the remaining osenv stuff in utils is file (osenv.Home, osenv.SetHome). Those functions in osenv/vars_* seem to be generic. We can either 1) move vars_* into utils (or perhaps utils/os), or 2) break the file stuff in into a separate pkg
[11:06] <rogpeppe> pwd
[11:10] <rogpeppe> frankban: i think all the proxy-related stuff should move out of osenv and into utils/proxy (httpproxy?)
[11:10] <rogpeppe> frankban: i think osenv.Home() should move out of osenv too
[11:10] <rogpeppe> frankban: and SetHome too
[11:10] <rogpeppe> frankban: which would leave osenv with just juju-related stuff
[11:12] <frankban> rogpeppe: yeah, ok so I'll start with osenv home stuff. What do you thing about osenv.(Set)Home --> utils/os.(Set)Home?
[11:13] <rogpeppe> frankban: tbh they're trivial enough that perhaps they could go into utils itself
[11:13] <rogpeppe> frankban: utils already depends on os and has os-specific files
[11:15] <frankban> rogpeppe: ok so just osenv.(Set)Home --> utils.(Set)Home, correct? and later osenv.Proxy* -> utils/proxy.Proxy*, correct?
[11:15] <rogpeppe> frankban: sgtm
[11:16] <frankban> rogpeppe: cool, thanks, I'll start with the first one
[11:20] <rick_h_> morning all
[11:27] <rick_h_> morning rogpeppe can you add a card to the board for the apt refactoring you mentioned please? We've got a card in the ready to code lane for "migrate juju utils package" but sounds like we're doing parts of that so maybe just a new card?
[11:28] <rogpeppe> rick_h_: will do. that occurred to me earlier but didn't make it as far as motor action :-)
[11:28] <rick_h_> rogpeppe: hah, TGIF 
[11:30] <rick_h_> redir: when you get settled this morning can we catch up on where we're at for the demo prep stuff?
[11:54] <frankban> rogpeppe: moving Home to "utils" causes an import loop, it seems I am blocked on your apt change, unless I use a submodule e.g. utils/env
[11:55] <rogpeppe> frankban: i've proposed my apt change: https://codereview.appspot.com/100730044
[11:58] <frankban> rogpeppe: cool I'll take a look after lunch
[11:58] <rogpeppe> frankban: it's just been LGTM'd
[11:58] <frankban> rogpeppe: even better
[11:58] <rogpeppe> frankban: i'm about to approve it - it should hopefully have landed by the time you've finished lunch
[11:59] <frankban> rogpeppe: sounds good
[11:59]  * frankban lunches
[12:20] <rogpeppe> frankban: it's now merged
[12:32] <bac> thanks for the review frankban.  good suggestions.
[12:34] <bac> frankban: as an aside, i notice the quickstart tests have a failure if JUJU_HOME is set.
[12:41] <frankban> bac: yw
[12:41] <frankban> bac: confirmed, the expected error in test_no_admin_secret_found should use settings.JUJU_HOME
[12:42] <bac> frankban: ah, that's a simple way to fix it.  you want me to roll it into my branch?
[12:42] <frankban> bac: yes please
[12:42] <frankban> thanks
[12:42] <bac> gladly
[12:43] <bac> really freaked me out last night when lbox failed b/c i'd inadvertantly run it in another terminal...
[12:54]  * rogpeppe goes for lunch
[13:01] <redir> rick_h_: sure
[13:01] <redir> settled
[13:01] <rick_h_> redir: cool, how goes? It looked like you had mongodb conflict between the state server and mongodb for charmworld yesterday?
[13:01] <redir> and rick_h_ I don't know that it is a conflict
[13:02] <rick_h_> ok, but we suspect? 
[13:02] <redir> I can't start it with service but can by calling the command from the service config as the correct user 
[13:02] <redir> so I don't know what is preventing it.
[13:02] <rick_h_> redir: I was going to suggest can we test it out on two machine then? put the gui on the bootstrap node, but all of charmworld on a second
[13:02] <rick_h_> redir: to clarify if the dual mongos is the issue?
[13:03] <redir> so quickstart and then deploy CW to a separate instance?
[13:03] <redir> this makes using AMIs more difficult
[13:03] <redir> but not impossible
[13:03] <redir> and I would like to know why it isn't starting
[13:04] <redir> bac did you have a chance to look?
[13:04] <bac> redir: i did not
[13:04] <rick_h_> redir: well, let's get the process and the ami thing might not work out
[13:05] <bac> frankban: i did a 'make clean' in quickstart and now unrelated websocket tests fail, even in trunk.  have you seen that before?
[13:05] <bac> redir: i'm about to wrap up this task and then can help
[13:06] <frankban> bac: no, trying
[13:06] <bac> frankban: http://paste.ubuntu.com/7505527/
[13:06] <frankban> bac: confirmed and weird
[13:07] <bac> frankban: so some package shifted beneath us?
[13:08] <frankban> bac: we specify the version for each requirement, looking at the test
[13:10] <frankban> bac: but not for the websocket client, which is a dependency of python-jujuclient
[13:13] <bac> frankban: websocket's connect is never called in that test.  self.sock remains None.
[13:14] <frankban> bac: jujuclient 0.17.5 has install_requires=["websocket-client"], without the version :-/
[13:15] <frankban> bac: and a new version of the websocket client has been released recently
[13:15] <bac> ah
[13:15] <frankban> bac: newer versions of jujuclient fix it, but we must depend on  0.17.5 which is the trusty release
[13:16] <bac> uh-oh
[13:16] <bac> frankban: they 'fix it' by specifying the websocket version or a code work-around?
[13:17] <frankban> bac: install_requires=["websocket-client==0.12.0"],
[13:17] <frankban> bac: which is correct, 0.12.0 is the trusty release
[13:17] <bac> frankban: can we add that to quickstart?
[13:18] <frankban> bac: so, the easy fix is to add websocket-client as a dependency in requirements.pip, even if it's not a direct dependency
[13:19] <frankban> bac: setup.py automatically adds the requirements listed in requirements.pip
[13:20] <bac> frankban: verified that works
[13:20] <frankban> bac: cool
[13:20] <bac> frankban: i'll XXX to remove it when we go to a newer version of jujuclient
[13:21] <frankban> bac: sounds good thanks
[13:27] <rick_h_> frankban getting some <3 in the comments http://hackingdistributed.com/2014/05/22/hyperdex-on-aws/
[13:28] <bac> frankban: created new module quickstart/platform_support.py .  it is a little unwieldy but i could not shadow the stdlib platform module.
[13:28] <frankban> rick_h_, jcastro: cool!
[13:29] <redir> there's no juju noop command is there?
[13:29] <redir> one that prints what it would do but doesn't actually do it?
[13:32] <frankban> bac: platform_support sounds ok, I suggested platforms but I agree is too similar to the stdlib one. from PEP8: "Underscores can be used in the module name if it improves readability.". I think this is the case
[13:32] <frankban> redir: I am not aware of any dry run mode
[13:43] <redir> frankban: tx
[13:44] <bac> frankban: requested changes made and ready for review at https://codereview.appspot.com/99410054/
[13:45] <frankban> bac: looking
[13:46] <redir> frankban: tx
[13:46] <redir> echo
[13:46] <frankban> redir: yw yw
[13:50] <bac> rick_h_: standup shouldn't go long today, should it?
[13:50] <rick_h_> bac: nope
[13:50] <rick_h_> bac: just normal run through and we've got two weekly review
[13:50] <bac> good.  going to tour CG cutter at 11:45
[13:50] <rick_h_> gotcha
[13:51] <rick_h_> bac: will try to move fast today
[13:55] <redir> I'd like to find a way to fail faster:/
[13:57] <frankban> bac: done
[14:02] <redir> what does: An error occurred while deploying the bundle: error() takes exactly 2 arguments (4 given) mean
[14:03] <redir> in jujugui
[14:03] <rick_h_> redir: it means something didn't go according to plan. I bet the deployer doesn't like some error handling code
[14:04] <rick_h_> redir: want to hangout and see what's up? 
[14:04] <hazmat> hmm
[14:05] <redir> just started different bundle... but I htink I can reproduce
[14:05] <bac> redir: i'm available now to help.
[14:05] <redir> I prolly have something wrong in some bundle
[14:05] <redir> I am here
[14:05] <rick_h_> redir: yea, but we probably have something wrong is surfacing that error to the user behind the gui
[14:06] <redir> ok gimme about 10 minutes to see if this deploy succeeds
[14:06] <rick_h_> k
[14:06] <hazmat> redir, found it
[14:07] <hazmat> redir, the bundle had an invalid placement  fwiw
[14:08] <hazmat> redir, can you pastebin the bundle
[14:11] <redir> hazmat: sure
[14:15] <redir> hazmat: 
[14:16] <redir> http://paste.ubuntu.com/7505780/
[14:16] <hazmat> redir, so for placement onto another service.. you have to specify for each unit the remote service unit.
[14:17] <hazmat> hmm
[14:17] <hazmat> your syntax looks sane though
[14:18] <hazmat> redir, try with to: [mongodb]   
[14:18] <redir> hazmat: I have modified it about 100 times
[14:18] <hazmat> redir, you mean you've already tried that suggestion?
[14:18] <redir> so rerunning to verify
[14:18] <redir> hazmat: I believe so
[14:18] <hazmat> redir, like 10 and 19
[14:19] <redir> http://paste.ubuntu.com/7505793/
[14:19] <hazmat> redir, that works
[14:19] <redir> hazmat: that one works to put all services on one machine "0" if previously bootstrapped
[14:20] <redir> but mongo doesn't start
[14:20] <hazmat> redir, and the log says?
[14:20] <hazmat> for mongo that is
[14:20] <redir> so I am now trying to deploy the 3 services in the bundle to 1 other machine
[14:20] <redir> mongo the log says nothing no log created in /v/l/m/m.log
[14:20] <hazmat> redir, also check /var/log/upstart/mongodb.log
[14:21] <redir> doesn't start using service ... start either
[14:21] <redir> hazmat: doh, forgot about that other log location:/
[14:23] <hazmat> the whole charm world deploy and ingest world to support the gui is kinda of bogus
[14:23] <redir> hazmat sadly that time the bundle didn't get the error
[14:23] <hazmat> redir, why so glum chum ;-)
[14:23] <hazmat> sledgehammer to cut cheese..  style
[14:24] <redir> you've pointed me at that upstart log dir before and I forgot about it
[14:25] <redir> An error occurred while deploying the bundle: read tcp 127.0.0.1:37017: i/o timeout
[14:25] <redir> doesn't look ideal
[14:26] <frankban> rogpeppe: are you available for reviewing https://codereview.appspot.com/98510043 ?
[14:26] <rogpeppe> frankban: looking
[14:26] <frankban> rogpeppe: thanks
[14:34] <hazmat> redir, its juju state server on the fritz, it comes back. but the deploy needs to be reattempted
[14:34] <hazmat> redir, your running two mongodbs, juju state server, charmworld trying to ingest the universe.. its quite a heavy workload for a single machine
[14:35] <hazmat> oh.. and java elasticsearch
[14:35] <redir> hazmat: on that deploy there are two machines
[14:35] <hazmat> redir, to=0 ?
[14:36] <redir> the one with the 37017 i/o fail is on m0 and es/cw/mongo are on m1
[14:36] <redir> but es failed to show up on that one
[14:36] <redir> hazmat: bac I'd be glad for eyes on these two envs I have running
[14:36] <hazmat> redir, are you using canonistack?
[14:37] <redir> hazmat: uh probably not
[14:37] <redir> ec2
[14:37] <hazmat> redir, cool
[14:38] <redir> hazmat: bac invites sent if you are free
[14:38] <redir> https://plus.google.com/hangouts/_/gyagopwm6fdrxuvnl6oaqdjhoya?authuser=3&hl=en
[14:50] <rick_h_> jujugui call in 10
[14:50] <hazmat> redir, sorry stepped away.. no one was there
[14:58] <rick_h_> jujugui call in 2 kanban and such please
[15:01] <rick_h_> frankban: rogpeppe Makyo ^
[15:06] <Makyo> jujugui Review/QA: https://github.com/juju/juju-gui/pull/340
[15:10] <bac> redir: i'm running an experiment on ec2 to see if i can manually deploy mongo to machine 0
[15:21] <hatch> another week almost down....man these weeks fly by
[15:22] <rick_h_> yea, no kidding
[15:23] <frankban> hatch: its seems Y.merge is shallow and clone is deep copy: http://yuilibrary.com/yui/docs/api/classes/YUI.html#method_clone
[15:24] <hatch> doh!
[15:24] <hatch> sorry everyone!
[15:24]  * hatch sulks away
[15:24] <hatch> ^ jujugui
[15:25] <frankban> hatch: :-) np, I was just wondering why my Y.clone fix worked two weeks ago
[15:27] <rick_h_> :)
[15:28] <bac> rogpeppe, redir: http://paste.ubuntu.com/7506019/
[15:32] <hatch> ok....what's it going to cost me to get someone to write these tests.....?
[15:32] <hatch> :P
[15:34] <hatch> rick_h_ btw - maybe I like the token widget now
[15:34] <hatch> MAYBE
[15:35] <hatch> :-)
[15:40] <rick_h_> hatch: hah, just a matter of time :P
[15:41]  * rick_h_ is going to get a t-shirt made up "Jeff says 'maybe..mabye rick was right" :P
[15:42] <hatch> lol
[15:52] <hatch> rick_h_ I can now reproduce Makyo's bug - We need to ignore the inflight response because the 'store' abstraction doesn't return the actual XHR pointer
[15:53] <rick_h_> hatch: right, I think we chased that before
[15:54] <hatch> the 'proper' fix would be to fix the store abstraction I think - but we can do a workaround for now, I'll do it in a follow-up
[15:54] <rick_h_> hatch: cool, yea I think a sanity check to just have the response come back and note the container is gone, halt, would beok
[15:55] <rick_h_> hatch: it's almost same effect as inflight ignoring because it's not like the server stops 
[15:55]  * redir orders some lunch then wants to chat with rick_h_ to work out plan for this and handoff/knowledge transfer
[15:55] <rick_h_> redir: ok, are we chatting before lunch or after it?
[15:55] <hatch> right right - it would be nice though from the destructor to be able to call something like 'inflight.cancel()' though
[15:56] <rick_h_> hatch: right, but then it needs access to the store internals 
[15:56] <redir> your choice rick_h_ 
[15:56] <rick_h_> hatch: it's a bit dirty
[15:56] <hatch> rick_h_ well no, the store calls could return a reference to the call
[15:56] <hatch> just like the env does
[15:56] <rick_h_> hatch: k
[15:56] <rick_h_> redir: let's do before then while it's fresh in our heads
[15:56] <hatch> this might be one of those 'just' things which turns into a big job hah
[15:56]  * rick_h_ is going to be shutting down after lunch friday ugh
[15:56] <hatch> so workaround first
[15:57] <rick_h_> hatch: I have a feeling like I chased that down before and hit that wall 
[15:57] <redir> OK
[15:57] <hatch> tis possible
[15:57] <redir> let me make a biobreak and I am ready
[15:57] <rick_h_> hatch: this has the smell of promises causing doom to it
[15:58] <rick_h_> hatch: I think that's what I hit, some of the store calls are wrapped with promises that have specific return values already
[15:58] <hatch> haha I thought we got rid of promises, or are they still in there?
[15:58] <rick_h_> and getting at a reference to the ajax call isn't easily done
[15:58] <rick_h_> we stopped creating more, we never cleaned out the old ones
[15:58] <hatch> oh I thought we did
[15:59] <rick_h_> https://github.com/juju/juju-gui/blob/develop/app/store/charmworld.js#L280
[15:59] <rick_h_> and more
[16:01] <hatch> ohh boy
[16:01] <hatch> promises - the gift that keeps on giving
[16:01] <redir> rick_h_: ready and in daily HO
[16:01] <rick_h_> hatch: ok otp
[16:05] <redir> rick_h_: http://paste.ubuntu.com/7506167/
[16:11]  * rick_h_ goes to get food
[16:12] <hatch> rebase is nice when you want to re-order commits
[16:19] <rick_h_> yep yep
[16:37] <rick_h_> redir: woot, that bundle came up for me
[17:15] <hatch> ugh edge case
[17:15] <hatch> for the amount of pixels this takes up on a screen there are sure a lot of cases
[17:15] <rick_h_> :)
[17:16] <redir> rick_h_: with ~cs:charmworld?
[17:16] <redir> or with bac's branch?
[17:16] <rick_h_> redir: both
[17:16] <rick_h_> redir: I used your bundle first as it was
[17:16] <redir> rick_h_: failed for me with bac's branch
[17:16] <rick_h_> and I've just finished a second pass with the source set to lp:charmworld
[17:16] <redir> I must have the spelling wrong
[17:17] <rick_h_> redir: I downlaoded it and then just passed it to juju-quickstart
[17:17] <rick_h_> redir: so not sure
[17:17] <rick_h_> you pasted it right :)
[17:17] <rick_h_> redir: have some basics for the local charm docs? I'll try it out on my env I've got here
[17:18] <redir> rick_h_: actually I need some local charms:)
[17:18] <rick_h_> charm get XXX
[17:18] <rick_h_> using charmtools
[17:18] <redir> oh
[17:18] <rick_h_> will fetch them down and such
[17:18] <rick_h_> brb
[17:18] <redir> rick_h_: how can I be sure it would deploy my charm rather than one ingested?
[17:20] <rick_h_> redir: you're not tryuing to deploy it
[17:21] <rick_h_> this is all eye candy, to get a charm into charmworld and then the gui will show it in the top left of the sidebar
[17:22] <redir> oh
[17:23] <bac> redir: how goes the battle?
[17:24] <rick_h_> hey bac side note, do you still have hte apache log info on the mjc traffic? IS asked me to get an RT filed to investigate the traffic and get it corrected and I want to make sure to fill in the fact right
[17:25] <bac> rick_h_: i have anonymized apache logs from the other day. thedac just got it for me with no RT.  is that what you want?
[17:25] <rick_h_> bac: yes, I just want to get the facts together. Knowing thedac helped look is good info. 
[17:26] <bac> rick_h_: i can paste some representative entries or give you the whole 22M compressed file
[17:26] <rick_h_> bac: a couple reference points will be good. Mainly I want to make sure we are positive where the traffic was from before filing the RT and how we figured out what was up
[17:27] <rick_h_> bac: or I was going to rope you into sumitting the RT and copying me on it if you don't mind/have time
[17:27] <rick_h_> bac: but on the bundle front I've had two good deploys from quickstart the colocated bundle redir put together and we're getting ready to test the local charm ingestion part
[17:30] <bac> rick_h_: it was positively identified by the user-agent being gsa-crawler.  thedac then looked at the non-anon IP address and saw it was internal.
[17:30] <rick_h_> bac: ok 
[17:33] <bac> rick_h_: http://paste.ubuntu.com/7506455/
[17:33] <rick_h_> bac: thanks, appreciate the details
[17:34] <bac> rick_h_: but IS already took some action to scale back the load caused by the crawler.  would be worth a check to see if it has helped.
[17:41] <bac> rick_h_: do you want me to file an RT?  if so, what are we requesting?  that they look at the log files to see if they are causing excessive load or that they not index the sites at all?
[17:41] <rick_h_> bac otp, I'll file in a bit
[17:41] <rick_h_> bac: they want to see why it's crawling at all
[17:41] <bac> rt
[17:41] <bac> ah, best plan
[17:42]  * rogpeppe is done for the day
[17:42] <rogpeppe> see y'all tuesday
[17:42] <rick_h_> have a good weekend rog
[17:43] <rogpeppe> rick_h_: and you. and happy weekends to everyone else too!
[17:48] <redir> later rogpeppe 
[17:53] <redir> rick_h_: otp?
[17:55] <rick_h_> redir: yea on the phone
[18:02] <redir> bac got a sec?
[18:02] <bac> i do
[18:02] <redir> regualar channel or should I start one?
[18:02] <bac> hatch: thanks for the tip about iterm2.  urwid works fine on it.
[18:02] <bac> redir: regular
[18:02] <hatch> awesome
[18:02] <hatch> yeah it's by far the most popular terminal client on osx
[18:42] <rick_h_> redir: how we doing? I've got a 15min break here
[18:45] <redir> good
[18:45] <redir> wanna follow up after your call or have a look?
[18:46] <rick_h_> redir: sounds good
[18:47] <redir> which?
[18:48] <rick_h_> oh, follow up after hte interview 4pm ish (hopefully a bit earlier)
[18:48] <redir> OK
[18:48] <redir> perfect
[18:48] <rick_h_> sorry, read that as "after your call have a look"
[18:48] <rick_h_> come on friday!
[18:50] <redir> np
[18:50] <redir> I  shouldhn't ask compound questions
[18:59] <hatch> I wish YUI had a deep comparitor
[19:07] <hatch> edge case.....SMASHED
[19:07] <hatch> boo yeah
[19:11] <hatch> oh that just broke everything outside of il
[19:11] <hatch> head....desk
[19:17] <hatch> apparently this render editorial and sidebar business is ingrained into the browser deeper than I had thought
[19:26] <redir> rick_h_: I have to run two errands before things close. I should be back by 4
[19:26] <rick_h_> rgr
[19:27] <hatch> The Witcher 2 is only $4 and avail on Linux
[19:27] <hatch> http://store.steampowered.com/app/20920/
[19:28] <rick_h_> hatch: cool or need to chat?
[19:29] <rick_h_> redir: cool, I'm free when you get back
[19:29] <hatch> rick_h_ all good - I just need to add a bunch of code back in which is causing cascading test failures
[19:29] <hatch> and tackle them in a follow-up
[19:29] <rick_h_> gotcha
[19:29] <rick_h_> yea, smaller is better in this process
[19:32] <hatch> rick_h_ I can also just put a patch in and break non il
[19:35] <hatch> actually I can just fudge these tests
[19:43] <hatch> rick_h_ no wonder this didn't work out going whole hog on it heh
[19:43] <hatch> it's all so intertwined in ways that aren't immediaately apparent until you break it :)
[19:43] <rick_h_> yea, I make bad decisiosn so you don't have to
[19:43] <rick_h_> :)
[19:43] <hatch> lol
[19:43] <rick_h_> decisions that is
[19:48] <hatch> excellent, back to where I was 2h ago
[19:48] <rick_h_> heh, baby steps
[19:49] <hatch> heh it's funny when tests pass but the code their testing doesn't exist
[19:49] <hatch> too much stubbing
[19:49] <hatch> lol
[19:49] <rick_h_> yea, I'm nervous with the level of stubbing we're getting to
[19:50] <hatch> once we go to a folder based, test hierarchy it will be a lot easier to see where our tests are and how they integrate 
[20:02] <redir> rick_h_: I am back
[20:02] <rick_h_> redir: cool
[20:02] <rick_h_> redir: https://plus.google.com/hangouts/_/gqvoo43tsgwyvpgcdtinfcjdema?authuser=1&hl=en
[20:40] <redir> rick_h_: https://dl.dropboxusercontent.com/u/7386012/cw-2instance-demo.tar.bz2
[20:41] <redir> rick_h_: lemme know when you grab it
[20:41] <rick_h_> redir: rgr
[20:41] <redir> I'll remove after
[20:41] <rick_h_> redir: got it, extracted and can read the readme
[20:42] <rick_h_> redir: thanks again for working on that and getting your juju crash course in :)
[20:46] <hatch> passing tests.....victory
[20:47] <hatch> now to see if it still works
[20:47] <hatch> lol
[20:47] <rick_h_> hah I was going to ask if it'll pass review and qa
[20:48] <redir> rick_h_: want me to leave that stuff running in aws?
[20:49] <rick_h_> hatch: I will say let's see next week if this is still a problem if we can start a parallel path vs refactor
[20:49] <rick_h_> redir: nope, you're good thanks
[20:49] <redir> OK rick_h_ then I am going to destroy that environment.
[20:50] <rick_h_> redir: sounds good
[20:50] <hatch> rick_h_ which problem?
[20:50] <hatch> rick_h_ https://bugs.launchpad.net/juju-gui/+bug/1322744 maybe we want to make luca aware of this bug
[20:51] <_mup_> Bug #1322744: Entering a text search query after selecting category restricts search to that category silently <juju-gui:New> <https://launchpad.net/bugs/1322744>
[20:51] <rick_h_> hatch: this refactor, if we can't get the stuff to work with flags on and off we build a diff code path 
[20:51] <rick_h_> hatch: we've talked about it. It'll go away soon
[20:51] <hatch> the filters?
[20:51] <rick_h_> that's an existing bug actually, /me looks for it
[20:52] <hatch> ohh ok
[20:52] <rick_h_> hmm, no luck. Well yes it's a know ux failure that will go away but we live with for now
[20:52] <hatch> rick_h_ ok so doing the QA after I have it working properly under il the charmbrowser now no longer works without il
[20:52] <redir> rick_h_: also leaving that card in the code column if you are working on it still
[20:53] <rick_h_> redir: ok thanks I am
[20:53] <rick_h_> hatch: https://plus.google.com/hangouts/_/canonical.com/mark-rick?authuser=1
[20:55] <bac> redir: how goes the battle?
[20:56] <redir> thanks bac, rogpeppe, and hazmat for all your assists navigating the juju/quickstart/deployer/bundle jungle
[20:56] <redir> bac done I think
[20:56] <redir> bac rick_h_, is adding a couple more things to it 
[20:57] <redir> bac I updated your doc a little to. To reflect using juju scp -- -r ...
[20:57] <redir> and also to use local-charms directories with valid series names
[20:57] <bac> redir: thanks.  that knowledge came afterwards and i forgot to update
[20:57] <redir> np
[20:57] <bac> redir: i think we need to file a juju-core bug about mongodb on node 0
[20:58] <redir> bac and one about controlmaster:)
[21:00] <hatch> rick_h_ in case you were interested here is the branch with all the new tests and whatnot https://github.com/juju/juju-gui/pull/342
[21:01] <rick_h_> hatch: k, I'll probably not peek until monday to be honest
[21:01] <rick_h_> brain fry setting in
[21:02] <hatch> yeah np, it's almost a 1000 line diff but a big chunk of that was the removal of the original search results list test suite
[21:02] <bac> redir, rogpeppe: bug filed -- https://bugs.launchpad.net/juju-core/+bug/1322747
[21:02] <_mup_> Bug #1322747: Deploying mongodb to machine 0 fails <juju-core:New> <https://launchpad.net/bugs/1322747>
[21:04] <hatch> rick_h_ oh ok I know why it doesn't render now - just looking into how much work it'll be to fix it
[21:05]  * rick_h_ runs off to get the boy from day care. Have a good weekend all if I don't see you alter
[21:05] <rick_h_> later
[21:05] <hatch> enjoy!
[21:09] <hatch> nice....fixed it
[21:26] <hatch> jujugui looking for two reviews and qa's on https://github.com/juju/juju-gui/pull/342 plz and thanks
[21:48] <hatch> anyone still in?
[21:49] <rick_h_> Makyo: email on the way
[21:49] <rick_h_> hatch: don't think so, TGIF
[21:49] <hatch> haha, well my branch is finished and up for any takers if they want over the weekend
[21:49] <hatch> I'm going to continue on it for the next card
[21:49] <hatch> on a new branch from it that is
[21:49] <rick_h_> dude, go enjoy the weekend :P
[21:50] <hatch> I still have an hour!
[21:50] <rick_h_> we'll catch up on monday and I'll help review/qa it
[21:50] <hatch> and it's +30C, way to hot!
[21:50] <rick_h_> lol
[21:50] <rick_h_> then go slack or play with go or the python stuff 
[21:50] <rick_h_> or take a nap
[21:50] <rick_h_> those are good when it's hot :P
[21:50] <hatch> go put on some SPF 110 and head outside
[21:50] <hatch> lol
[21:50] <rick_h_> there you go
[21:50] <rick_h_> mow the lawn!
[21:51] <hatch> yeah it does need some mowing
[21:51] <hatch> ok gong to mow the lawn
[21:52] <hatch> you convinced me
[21:52] <rick_h_> and with that, the invites out, ty Makyo for the assist, and I'm going to run away as well
[21:52] <rick_h_> lol
[21:52] <rick_h_> glad my feedback works on lawns
[21:52] <rick_h_> (that I can't see)
[21:52] <hatch> haha - enjoy your weekend
[22:16]  * redir heads to pack. This time tomorrow I'll be sitting on a beach with a margarita or something... see you all in a week.
[22:16] <redir> or so