[12:52] <bac> hi teknico, frankban
[12:53] <bac> teknico: does "go env |grep GOPATH" actually show your GOPATH as in the juju-core README?  i've set mine but it isn't being shown.
[13:01] <bac> teknico: nm.  'go env' doesn't show it but my GOPATH is being used
[13:49] <gary_poster> bcsaller_, hatch, Makyo|out I think we are ready for the (probably relatively short) Landscape kickoff call I mentioned Monday.  Let's plan to do it before the daily call when Makyo|out joins--probably no later than 1:11 from now (1500 UTC)
[13:49] <bcsaller_> gary_poster: sounds good
[13:49] <gary_poster> thx
[13:51] <hatch> sounds like a plan
[13:58] <hatch> oo those designs are sexy
[14:05]  * hazmat tries out the gui in opera for kicks
[14:06] <hazmat> sadness
[14:07] <hatch> yeah? what breaks?
[14:08] <teknico> bac, yes, same conclusions
[14:09] <hazmat> hatch, js error on initial connect, quite a few style errors
[14:09] <bac> teknico: thx
[14:09] <hazmat> hatch, basically a blank page
[14:09] <hazmat> we have a helpful page intro page saying use chrome... 
[14:10] <hatch> hazmat: oh haha, with my limited Opera experience usually they do things 'to the book' meaning that if anything is done even a little off spec it breaks :)
[14:11] <hazmat> hatch, yeah... makes them a nice validation tool.. here's the js traceback. http://pastebin.ubuntu.com/1643873/
[14:12] <hazmat> css errors http://pastebin.ubuntu.com/1643884/
[14:13] <hazmat> was curious cause they just announced they'll be moving to webkit and chromium as a base
[14:15] <benji> gary_poster: I did not realize yesterday that you were telling me that I had not followed the flow chart.  I did not realize that there were to be two messages.
[14:16] <benji> To clarify/verify: there are to be *two* loading messages: one that says that the application is loading and after that one that says that we are connecting to the environment.
[14:17] <gary_poster> benji, yes.  as I said, sympathetic to what you did.  If we can do the second message, though, potentially compelling.
[14:18] <benji> I can do anything given enough time and money. ;)
[14:18] <hatch> hazmat: oh yeah I forgot that it throws errors for unknown prefixed properties heh
[14:19] <gary_poster> benji, right.  timebox it to two hours, let's say?
[14:19] <benji> k
[14:19] <benji> And I'll money-box it so I spend no more than $100,000,000.  Just like normal.
[14:20] <gary_poster> benji :-P
[14:20] <hatch> but if it's incomplete at $100M then you can requisition more to get it completed....just like the government :P
[14:24] <benji> :)
[14:25] <hatch> it's snowing....1" so far!
[14:35] <frankban> bac, teknico: https://code.launchpad.net/~jtv/juju-core/no-go-env/+merge/142280
[14:37] <bac> frankban: nice.  too bad it stalled.
[14:38] <hazmat> does anyone have emacs config for our current style guide handy?
[14:38] <teknico> frankban, nice, thanks
[14:39] <bac> hazmat: i have an incomplete emacs config.  it sometimes formats in ways that cause the linter to complain.
[14:40] <bac> frankban, teknico: i added a comment to jtv's MP asking him to please land.  we'll see.
[14:41] <hazmat> bac, that would help .. feel like i'm fighting emacs more than coding atm
[14:41] <frankban> cool bac, thanks
[14:41]  * hazmat wonders if its time to give sublime a shot
[14:42] <hatch> I'm really irritated with the dev of sublime so although I use it I probably won't be upgrading
[14:43] <teknico> hazmat, hey, please don't kill it yet, I still need it! ;-)
[14:43] <teknico> hatch, why the irritation, if I may?
[14:44] <hazmat> hatch, because of charge for upgrade? better than promising free like tmxt2 and loosing motivation
[14:45] <hatch> teknico: well around the middle of last year he basically drops off the earth - doesn't respond to any requests about the editor or updates. Then just recently comes out with a new version out of the blue and for people who 'recently' bought, he is charging a fee which makes it more expensive than if they had waited a week
[14:45] <hatch> I don't have any issue paying to upgrade - but his actions make it clear that the community isn't important
[14:46] <frankban> hazmat: re gojuju workflow: how do you update trunk after cobzr has been used (i.e. after lightweight checkouts has been created)? "bzr switch master && bzr pull lp:juju-core (--remember)" from the juju-core dir? bzr pull from .cobzr/master and the update?
[14:47] <bac> hazmat: http://paste.ubuntu.com/1644110/  -- like i said it is hacky and not complete.  improvements welcome.
[14:47] <hazmat> frankban, go get juju-core/package/...
[14:47] <hazmat> frankban, the triple dot syntax is update recursive deps
[14:48] <hazmat> frankban, oh.. i haven't been using cobzr.. i'd ask on juju-dev
[14:48] <frankban> hazmat: ok thanks
[14:48] <teknico> hatch, I usually prefer using FLOSS tools, also to avoid these kinds of issues, but in this case the tradeoff seems reasonable, and the pricing terms described in his announcement seem reasonable overall
[14:49] <teknico> http://www.sublimetext.com/blog/articles/sublime-text-3-beta
[14:49] <hazmat> bac, thanks!
[14:49] <hazmat> rogpeppe, ^ frankban's question re cobzr
[14:49] <hatch> teknico: the pricing is an inconvenience - I'm mostly irritated at his handling of this new version
[14:50] <teknico> as far as disappearing, yes, anything that depends on just one person is somewhat worrying, FLOSS or not
[14:50] <hatch> when someone pays you for a product they expect support - and not responding to comments for 6months is not very good service
[14:50] <teknico> that's also true
[14:50] <teknico> good point, noted
[14:50] <bac> frankban: i think switching to master and doing a pull as you stated is correct.
[14:51] <hatch> so with all that said :) It's a very very good product which has me torn on the upgrade ;)
[14:52] <frankban> hum...  Sublime Text now uses Python 3.3 for plugins, wonder if I have to update my little plugin...
[14:55] <hatch> Makyo|out: when you return - the 'renderedHandler' in topology/service.js doesn't appear to have any effect on the application - maybe it's an artifact of an older version?
[14:55] <teknico> frankban, that's a plus in my book :-)
[14:59] <frankban> teknico: yes, but it can break my workflow! http://xkcd.com/1172/
[14:59] <hatch> frankban: lol
[15:01] <hatch> xkcd comics are funny because they are true :P
[15:07] <hatch> gary_poster: integration chat starting soon?
[15:08] <bcsaller_> I was wondering the same thing
[15:09] <gary_poster> bcsaller, hatch waiting on Makyo|out 
[15:12] <hatch> if you set the charm layout - resize the window - refresh - the charm layout stays the same even if the new window is too small
[15:12] <hatch> known bug?
[15:13] <gary_poster> hatch, new and intermittent.  If I keep readjusting it sometimes works. :-/
[15:14] <gary_poster> hatch you filing or shall I?
[15:14] <hatch> I already have it open :)
[15:14] <gary_poster> cool thanks :-)
[15:16] <gary_poster> hatch btw you can land bug 1123291 yeah?
[15:16] <_mup_> Bug #1123291: Update HACKING readme with missing details <juju-gui:In Progress by hatch> < https://launchpad.net/bugs/1123291 >
[15:16] <gary_poster> There you are _mup_!
[15:17] <hatch> sure let me just review the responses to make sure I got everything
[15:17] <gary_poster> hatch, bcsaller if Makyo|out is not around at call, let's just talk amongst ourselves after the daily call about it, and I can fill him in with the gist later
[15:19] <hatch> sure
[15:20] <hatch> maybe his window install didn't go so well
[15:20] <hatch> :)
[15:21] <bcsaller> gary_poster: in the hangout
[15:23] <hazmat> do we subscribe to the generic op events in the gui? or just use the op callbacks?
[15:27] <gary_poster> hazmat, bcsaller and I have a very limited idea of what you are talking about, but we think the answer is callbacks if we understood you :-)
[15:28] <gary_poster> jujugui call in 2
[15:30] <gary_poster> benji goodspud call now
[15:31] <benji> hmm, insuficient beepage
[15:42] <bcsaller> hazmat: you want to start another hangout?
[15:42] <bac> teknico_, frankban: do the juju-core tests pass for you?
[15:42] <Makyo> hatch, come baaaaack
[15:42] <hazmat> bcsaller, sure
[15:42] <gary_poster> heh
[15:43] <hazmat> bcsaller, old juju-gui ;-) ? tinyurl.com/juju-ui
[15:43] <teknico_> bac, I'm having problems with them right now, actually
[15:43] <bac> teknico_: me too.  and if i follow the instructions for speed up to run 'go test -i ...' it fails miserably and full of lies.
[15:44] <teknico> bac, that too, glad it's not just me, fwiw :-)
[15:44] <bac> yes, quite a comfort
[15:45] <gary_poster> bac, teknico I suggest pinging Roger (r o g p e p p e) but I won't do it for you because I'm not as far along as you all :-)
[15:46] <bac> gary_poster: ok
[15:46] <teknico> rogpeppe, ^^ any ideas?
[15:46] <rogpeppe> teknico: looking
[15:46] <rogpeppe> teknico: (just off a meeting)
[15:46] <gary_poster> would pastebin help?
[15:48] <gary_poster> hatch, saw your note about IE10 self-signed experience.  would love to hear more, yes
[15:48] <hatch> sorry that was in relation to the url state
[15:48] <gary_poster> oh ok
[15:48] <gary_poster> darn :-)
[15:49] <hatch> yeah sorry - I have absolutely 0 experience with self-signed cert with IE10 :)
[15:49] <teknico> rogpeppe, bac, here's my scrollback, fwiw: http://pastebin.ubuntu.com/1644452/
[15:50] <rogpeppe> teknico: are you running tests in trunk?
[15:51] <rogpeppe> teknico: because if you are, i'm afraid i broke the tests last night. :-/ i'm about to propose a branch that fixes it.
[15:51] <teknico> rogpeppe, the output of "cobzr branch" is "* master", if that's what you mean
[15:51] <teknico> rogpeppe, oh, that's good to know, thanks
[15:52] <rogpeppe> teknico: what's the most recent revno on your branch?
[15:52] <teknico> rogpeppe, 885
[15:53] <bac> rogpeppe: i'm at 887 and seeing the same failed tests
[15:55] <rogpeppe> bac, teknico: i've just merged a branch that at least means the test failures don't time out
[15:55] <bac> jujugui: i've created a google doc for tips/issues for us getting started with go.  unresolved ones can be fixes or bugs but i thought we could share experiences now.  please edit if you have stuff to add.  https://docs.google.com/a/canonical.com/document/d/1OEOzDu9lh4ko8oSgl_tjQlk98x_rgtiiSSJYBRopic8/edit?usp=sharing
[15:55] <rogpeppe> teknico: the rpc package will still fail its tests under Go 1.0.2, but the fix is coming soon
[15:56] <teknico> bac, thanks
[15:56] <bac> rogpeppe: if i run 'go test' it complains that some packages need to be updated and i should run 'go test -i' but when i do i get:
[15:56] <bac> go test -i launchpad.net/juju-core/...
[15:56] <bac> can't load package: package launchpad.net/juju-core: no Go source files in /home/bac/work/src/launchpad.net/juju-core
[15:56] <teknico> rogpeppe, thanks, trying
[15:56] <hazmat> rogpeppe, should we be running weekly?
[15:56] <gary_poster> cool thanks bac.  
[15:56] <gary_poster> we need new stuff from rog
[15:56] <rogpeppe> bac: that functionality only works with more recent versions of Go i'm afriad
[15:56] <hazmat> rogpeppe, is that fix 1.0.3 or 1.1?
[15:56] <rogpeppe> hazmat: which fix?
[15:57]  * bac lunches
[15:57] <hazmat> the rpc fix? trying to understand if we should be running weekly instead of stable
[15:57] <rogpeppe> hazmat: no. the rpc problem is because i was relying on 1.1-specific behaviour in json unmarshalling. i'm fixing it so it no longer does.
[15:58] <hazmat> ack
[15:58] <rogpeppe> hazmat: with a severe note-to-self to remind me to *always* run all tests against 1.1 *and* 1.0.2 before submitting :-)
[15:58] <teknico> hazmat, if those are Go version numbers, my installed packaged are 1.0.2-2
[15:58] <hazmat> rogpeppe, sounds like a job for continous integration tool
[15:59] <rogpeppe> hazmat: agreed. people have been working on that, but it's not there yet.
[16:13] <hatch> ok all changes to the HACKING document have been completed - now since i have already run `lbox propose -cr` do I need to do anything different this time to resubmit for review?
[16:13] <hazmat> bcsaller, re use db, how good is the gui currently about lots of updates? ie. should i still be batching.
[16:14] <Makyo> hatch Same command again.
[16:14] <hatch> is it common that I need to add 'make clean' ?
[16:14] <bcsaller> hazmat: if we need to debounce the update that would be  a simple change, for now I wouldn't worry about batching in the place you're dealing with it
[16:15] <hatch> I'll add make clean to the `submit for review` steps
[16:15] <Makyo> hatch, You shouldn't need too, since none of the made files are under rc.
[16:17] <teknico> rogpeppe, uhm, running "go test -gocheck.vv" in juju-core/state is still timing out like before on revno 888
[16:18] <rogpeppe> teknico: hmm, this is what i see: http://paste.ubuntu.com/1644622/
[16:18] <teknico> rogpeppe, oh, I think I know what it is
[16:19] <teknico> rogpeppe, hazm4t mentioned that MongoDb 32 bit does not support SSL
[16:19] <rogpeppe> teknico: ah yes. if you ran go test ./... -gocheck.vv,  you'd probably see a message
[16:19] <rogpeppe> teknico: you'll need to download the built version
[16:19] <hatch> hmm I'm a little confused by the `bzr log` command - I just 'committed' but that commit isn't showing up in `bzr log -r-5..`
[16:20] <hatch> is there a flag I'm missing?
[16:20] <rogpeppe> teknico: ah, 32 bit
[16:20] <teknico> rogpeppe, do you mean from http://juju-dist.s3.amazonaws.com/ ? No 32 bit versions there
[16:20] <rogpeppe> teknico: you'll need to compile it
[16:20] <rogpeppe> teknico: there's a charm to do that.
[16:21] <rogpeppe> teknico: unfortunately... 
[16:21] <rogpeppe> teknico: there's a bit of a chicken/egg situation here
[16:21] <teknico> indeed :-)
[16:22] <rogpeppe> teknico: if your machine has suitable horsepower, you could compile mongo on it
[16:22] <hatch> ahh `bzr log -l5`
[16:22] <teknico> rogpeppe, am I the very first unlucky fellow developing Juju on a 32 bit environment? sounds weird
[16:23] <rogpeppe> teknico: the recipe is in juju-core/cmd/builddb/precise/builddb/hooks/install
[16:23] <rogpeppe> teknico: noone has got around to generating a 32 bit exe, yeah. sorry about that.
[16:24] <teknico> rogpeppe, ok, next machine will get a fresh new 64 bit install :-)
[16:24] <Makyo> hatch, bzr alias ll="log --line -l10" is helpful
[16:24] <Makyo> hatch, then bzr ll
[16:24] <teknico> rogpeppe, ok, it seems doable
[16:25] <teknico> rogpeppe, does it have to be 2.2.0, or would 2.2.3 be preferable?
[16:25] <hatch> Makyo: pfft and yesterday I read a doc which said bzr had sane defaults and that's one reason it's better than git...lol
[16:25] <rogpeppe> teknico: i think you should probably go with the exact same version
[16:25] <teknico> rogpeppe, I will (yay for patch versions :-P )
[16:25] <Makyo> hatch, yeah, I found it helpful to just not really compare them, though apparently cobzr changes that some.
[16:26] <rogpeppe> teknico: you might want to spin up an ec2 instance to do the compilation - it's pretty intensive and takes some hours.
[16:27] <teknico> rogpeppe, wow, ok, thanks for the hint
[16:27] <rogpeppe> teknico: and once you've got the executable, it'd be great if you could sling a copy over to dave.cheney who can make it available in the public ec2 bucket
[16:27] <hatch> Makyo: ok back to getClientRect() - 1) load app 2) d-click charm 3) click juju to return 4) labels should be broken ?
[16:28] <teknico> rogpeppe, that sounds useful too :-) I will
[16:29] <Makyo> hatch, load app in Chrome and FF, click to view a service in chrome, create a relation to that service in FF, make sure there are no NaN errors in chrome's console, then click back to environment and make sure the labels look okay.
[16:29] <teknico> if mongo were written in Go, compiling it would probably be less resource-intensive :-)
[16:29] <Makyo> hatch Or just two separate tabs, I guess.
[16:29] <Makyo> hatch, just that Chrome's console is a little better.
[16:33] <hatch> yeah looks ok here I'll try a few different aproaches just to be sure
[16:33] <hatch> is it possible that this code was legacy?
[16:33] <hatch> was something upgraded or changed that could have made this legacy?
[16:38] <bcsaller> hatch: as a historical point, the whole environment view recently went through a fairly massive refactoring
[16:38] <hatch> alright :)
[16:38] <hatch> I just didn't want to remove this code if there was absolutely no possibility that it was fixed hah
[16:39] <Makyo> hatch, yeah, that's what I had mentioned on the call.  Used to get NaN problems in the svg.
[16:39] <hatch> yeah heh - ok I'll remove this code
[16:39] <hatch> yay for dead code removal!
[16:45] <gary_poster> hatch, Makyo, bcsaller are you all available for call now by chance?
[16:46] <Makyo> gary_poster, yes.
[16:46] <hatch> yep
[16:46] <bcsaller> gary_poster: yeah
[16:46] <hatch> in the board room?
[16:46] <hatch> :)
[16:46] <gary_poster> cool guys, let's go to jujugui
[16:47] <benji> it is unfortunate that the name of our hangout is the same as the interrupt-everyone-on-the-team-with-a-notification string
[16:47] <hazmat> agreed
[17:20] <gary_poster> bac benji you happen to be around and not lunching?
[17:20] <benji> gary_poster: yep
[17:20] <bac> gary_poster: yep
[17:20] <gary_poster> cool
[17:21] <gary_poster> frankban, teknico you around and available?
[17:21] <benji> just finishing up my merge; it was a mess with lbox and a prereq branch
[17:21] <teknico> gary_poster, yep
[17:21] <frankban> gary_poster: yes
[17:21] <gary_poster> cool, benji, bac, teknico frankban to the bat-cave! (juju gui)
[17:24] <hatch> will `bzr add editedfile.js; bzr commit -m "msg" ` commit only the added file? I have some edited files in this branch but I only want to commit one of them
[17:24]  * hatch is trying to apply git workflow to bzr again ;)
[17:27] <Makyo> hatch, bzr commit editedfile.js -m "msg"
[17:27] <benji> hatch: no, "bzr commit" will commit all outstanding changes
[17:27] <benji> what he said
[17:27] <hatch> eggcelent
[17:28] <Makyo> More like svn in that respect.
[17:28] <Makyo> Window guys are here, out for a sec.
[17:35] <hatch> jujugui - any objections to me removing the file assets/javascripts/svg-layouts.js ? the module in it is no longer needed and is being removed
[17:36] <bcsaller> hatch: I can't answer that without verifying usage 
[17:37] <hatch> I suppose - so there aren't any rules about removing files as long as it doesn't break anything? :)
[17:37] <Makyo> hatch, It's used twice in trunk, both in topology/service.js
[17:38] <hatch> yep - it's now used never in anything ;)
[17:38] <Makyo> hatch, Once is the area you removed, but what about the other?
[17:38] <hatch> the other area would break if it returned null
[17:38] <hatch> ex) null.width
[17:38] <hatch> so I reverted it to the 'original' method
[17:40] <hatch> I'll commit the code shortly for review
[17:40] <Makyo> hatch, we can do functional testing on it.
[17:42] <rogpeppe> juju trunk should be fixed now
[17:43] <rogpeppe> teknico, bac: ^
[17:43] <bac> rogpeppe: thx
[17:43] <teknico> rogpeppe, thanks
[17:45] <rogpeppe> unfortunately fixing it has meant that i'm not going to be proposing the watcher branch today
[17:46] <hatch> 100g yogurt containers are just too smal...they need a big-boy version.....300g!
[17:46]  * hatch just keeping the discussion on-topic
[17:59] <benji> hatch: you need horizontal scaling
[17:59] <hatch> but there is so much waste with the setup and teardown then
[18:00] <hatch> this is clearly a task for scale up not out ;)
[18:01] <hatch> Makyo: http://bazaar.launchpad.net/~hatch/juju-gui/1123426-getClientRect/revision/382
[18:12] <gary_poster> hatch, gave you a small extra review too :-P
[18:13] <hatch> lol damn - this is the last time I write documentation on something I know nothing about haha
[18:13] <teknico> famous last words :-)
[18:13] <hatch> lol
[18:15] <hatch> gary_poster: would you like me to split the shell command at 80 char as well?
[18:16] <gary_poster> hatch, only if it is still copy/pastable
[18:16] <hatch> ok I'll leave it then
[18:17] <hatch> so I understand these lboc propose messages https://gist.github.com/hatched/a99739e29af40314ab74
[18:18] <hatch> is the error on ln #2 and ln #57 normal?
[18:18] <hatch> that's the full output of the `lbox propose -cr`
[18:20] <hatch> I'm just updating the undocumented file right now
[18:20] <Makyo> hatch, http://pastebin.ubuntu.com/1645341/ on make devel
[18:22] <hatch> hmm
[18:22] <Makyo> bin/mergefiles (which calls lib/mergefiles.js, I think) is still looking for that file.
[18:23] <hatch> yep sorry I missed the -a flag on my `ack` command
[18:23] <hatch> I'll do another once over
[18:23] <hatch> just to be sure
[18:34] <hatch> could someone take a peek at this `lbox propose -v -cr` https://gist.github.com/hatched/a99739e29af40314ab74 it's failing on 'branch check'
[18:37] <hazmat> hatch, lbox runs  .lbox.check script in the branch root to verify the branch is clean/good
[18:37] <Makyo> hatch, it's failing on the linter.  You can run make lint to get the output, or make prep to have the beautifier try and fix it for you.  Looks like it's because renderedHandler is undocumented, but not in the list.
[18:37] <hazmat> can be run manually to verify
[18:38] <hatch> Makyo: are the entries in undocumented done by hand?
[18:38] <hatch> hazmat: ok thanks
[18:38] <Makyo> hatch, make undocumented, I think
[18:40] <hatch> ahh yes - the undocumented undocumented option
[18:40] <hatch> ;)
[18:41] <Makyo> hatch, I think it's more desirable to add documentation than add to the undocumented list.  make help though, will list targets, and instruct you toward the Makefile for other phony targets.
[18:44] <hatch> Victory!
[18:45] <hatch> I swear I'll get this workflow figured out
[18:49] <hatch> gary_poster: wrt HACKING -> do I now only need to commit and then `lbox submit` ? or do I need to push as well?
[18:49] <Makyo> lbox will push for you.
[18:50] <hatch> cool
[18:55] <hatch> benji: You created a task called "Extend Y.Node with svg support" - it actually already has it it just doesn't pass the methods through so you need to do node.getDOMElement().{svgmethod}
[18:55] <hazmat> benji, just noticed we login multiple times on the gui..
[18:56] <hazmat> two separate login requests right next to each other fwiw
[19:01] <benji> hazmat: hmm, I don't remember anything about svg; do you have a URL?
[19:01] <hazmat> svg?
[19:01] <benji> re. login; hmm, that sounds like a but
[19:01] <hazmat> just watching the improv script api calls
[19:02] <benji> s/but/bug/
[19:02] <hazmat> yeah.. filing one
[19:02] <gary_poster> what benji, svg is to hatch
[19:02] <benji> ah
[19:02] <gary_poster> s/what//
[19:02] <Makyo> hatch, benji, re: getting text from an SVG node?
[19:02] <hatch> https://canonical.leankit.com/Boards/View/102529849#/102902647
[19:03] <hatch> gary_poster: anything in particular you would like me to work on for the afternoon? I was thinking 1075656 would give me a really good idea of how the system works (although take longer than a day)
[19:04] <bac> after installing bigjool's mongo PPA i have success!  http://paste.ubuntu.com/1645668/
[19:05] <hazmat> cool
[19:05] <gary_poster> awesome bac.  
[19:05] <gary_poster> bug 1075656
[19:05] <_mup_> Bug #1075656: Charm panel should be YUI composite view, not closure <charmbrowser> <juju-gui:Triaged> < https://launchpad.net/bugs/1075656 >
[19:05] <gary_poster> hatch, yeah not good for today
[19:05] <hatch> ohh mup is a bot
[19:06] <hatch> :)
[19:06] <Makyo> hatch, re: svg elements: not sure that stands anymore.  We've (mostly) switched from the prior method to d3's classed method, but you can search for anything requiring utils.toggleSVGClass or whatever it was.
[19:06] <gary_poster> yeah :-)
[19:06] <Makyo> Also, can use d3 to get text of svg nodes rather than node.getDOMNode().firstChild.blah in tests.
[19:07] <gary_poster> hatch maybe easy and new stuff is bug 1123562.  Alternatively, choose something fast and IE
[19:07] <_mup_> Bug #1123562: selenium tests fail in firefox because of browser warning <juju-gui:Triaged> < https://launchpad.net/bugs/1123562 >
[19:07] <hatch> ok that's good to know, I'm definitely going to be reading up on d3 over the next few days
[19:09] <hatch> gary_poster: sure I can look into that one - although would not using a 'testing config' make more sense ? I am not keen on the idea of having code sitting in the app that's only used for testing being shipped to the client
[19:11] <gary_poster> open to different solutions.  that's another one, and can think of others.  quick call in juju gui?
[19:11] <hatch> you bet
[19:33] <benji> bac: where is this document about getting a go juju dev environment set up?  I've look through my email but I don't see anything.
[19:34] <bac> benji: it is in the google drive 'juju gui' folder.  direct link: https://docs.google.com/a/canonical.com/document/d/1OEOzDu9lh4ko8oSgl_tjQlk98x_rgtiiSSJYBRopic8/edit
[19:35] <benji> bac: thanks!
[19:35] <bac> benji: i didn't send an email...just pasted here.
[19:38] <bac> hazmat: go test complains that some packages aren't independently installed and thus slow things down.  but installing with 'go test -i' as suggested doesn't work.  'go get' doesn't work either.  list here: http://paste.ubuntu.com/1645904/  thoughts on how to properly get them installed?
[19:39] <bac> actually i should ask over at #juju-dev unless you know right off the top of your head
[19:46] <hazmat> bac, separately go get -u launchpad.net/goose && go get -u launchpad.net/goamz
[19:51] <bac> thanks hazmat.  this worked: go get -u launchpad.net/goamz/... && go get -u launchpad.net/goose/...
[19:55] <hazmat> cool
[21:10] <hatch> jujugui - any chance I can get some reviews of https://codereview.appspot.com/7306104/ so I can merge it before the end of day
[21:11] <Makyo> hatch, taking a look
[21:11] <gary_poster> I'm doing one too
[21:11] <hatch> thanks
[21:17] <gary_poster> hatch "land as is" from me. nice job
[21:17] <hatch> thank yaz
[21:18] <hatch> and its off!
[21:20] <hatch> when closing tickets is `lbox submit` mean "Fixed Release" or "Fixed Committed" ?
[21:21] <hazmat> hatch, its fixed release .. but you need to pass the bug in to lbox
[21:22] <hazmat> i think
[21:22] <hazmat> oh.. that's only propose
[21:22] <hatch> ok so I manually change them?
[21:23] <hazmat> hatch, it might do it if the branch is already linked to the bug not sure.. we have a secondary system (lp2kanban) that's trying to sync things back and forth as well
[21:23] <hazmat> but otoh, it might need manual intervention.. try and find out i guess.
[21:24] <hatch> ok next bug I work on I'll see what happens, some of these have been closed for a while and they haven't been automatically closed
[21:33] <gary_poster> hatch, change bugs to fix committed until we release.  thank you for cleaning those up though
[21:35] <hatch> cool and that getClientRect one gives me a lot of points
[21:35] <hatch> w00t w00t
[21:35]  * hatch marks all of his tickets secure
[21:37] <hatch> oh karma !== fire point value
[22:00] <hatch_> oops looks like the net went down
[22:02] <gary_poster> signing off.  bye all
[22:03] <hazmat> gary_poster, hmm. ran into an issue on the memory environment..
[22:03] <hazmat> raw yaml configs..
[22:08] <hazmat> hatch, nice!, first commit :-)
[22:09] <hatch> 2nd :)
[22:09] <hatch> well the first was just some css
[22:09] <hatch> :)
[22:15] <gary_poster> hazmat, ah! we can't send yaml to the env from charm deploy unless we go back to those bad js yaml libs?  We could simply disable that functionality. It's small, especially for playground
[22:15]  * gary_poster not really here.  disappearing again :-)
[22:17] <hazmat> gary_poster, yeah.. i'm just tossing error for now on that case. cheers
[22:45] <bcsaller> Makyo: it works w/o the queue I think :-/
[22:49] <Makyo> bcsaller, so it might've just been the async stuff?
[22:50] <hazmat> bcsaller, re using db directly, we're not subscribing directly to model events anywhere are we? else there's some strangeness possible because model event will fire before op callback gets invoked.
[22:50] <bcsaller> Makyo: it looks like it was an issue of timing
[22:50] <bcsaller> hazmat: we're not yet (with the exception of notifications), I'd like to but its still bound around the db.update event
[22:56] <hatch> 16GB macmini ram kit - awesome, I won't have to worry about my VM's crashing haha http://eshop.macsales.com/item/Other%20World%20Computing/1333DDR3S16P/
[23:04] <Makyo> USians - Monday's a holiday, correct?
[23:06] <hatch> Feb 18th is
[23:06] <hatch> :)
[23:07] <Makyo> hatch, yeah, just making sure it applies.
[23:08] <hatch> monday is a holiday here
[23:08] <hatch> no idea what for
[23:13] <hatch> Makyo: just saw your comments on the tickets
[23:13] <hatch> that's actually exactly why it's being moved into there
[23:13] <hatch> the search box
[23:14] <Makyo> hatch, Oh, so the tickets are for the redesign issues?
[23:14] <hatch> and then the splitting the charm panels are to allow for the design changes
[23:14] <hatch> yeah - the view code needs to be slightly refactored to make it easier to accomplish those changes
[23:15] <Makyo> hatch, Alright.  Keep in mind that other squads may be working on that portion of the project.
[23:15] <hatch> gary and I went over it this afternoon so I'm sure he can bring you up to speed on it tomorrow
[23:15] <hatch> oh yeah for sure
[23:15] <Makyo> hatch, Alright, it just wasn't clear from the tickets.
[23:15] <hatch> yeah sorry I kind of made the tickets for myself ;)
[23:18] <Makyo> hatch, and autocomplete?  I suppose we can do that with charmstore charms, since then we'll have a list outside, but otherwise, charms are loaded lazily.
[23:18] <hatch> so essentially how I envision that working is after load we'll request a list of all the available charms and display them in the search list
[23:19] <hatch> then there will be an input box which will filter the result list based on the users input
[23:19] <hatch> if the # of charms gets too large then we can easily switch it later to poll a server instead of a local dataset
[23:20] <Makyo> hatch, that's fair, but I think we should check next time we're all around where that fits in with current work, given that that would require either an update to core (of which there are a few now), or from a different source, such as the charm store.
[23:20] <hatch> oh yeah for sure - I think I marked that was as low priority
[23:20] <hazmat> which ticket?
[23:21] <hatch> https://bugs.launchpad.net/juju-gui/+bug/1124583
[23:21] <_mup_> Bug #1124583: Charm list should be an autocomplete result list <juju-gui:New for hatch> < https://launchpad.net/bugs/1124583 >
[23:21] <hatch> yep low
[23:21] <hazmat> hmm.. yeah. it was originally an auto complete list.. way back when..
[23:22] <Makyo> hazmat, Was there just a cs list to consume?
[23:23] <hazmat> Makyo, no it was an auto complete yui datasource hooked up directly to the charm store api
[23:23] <Makyo> hazmat, Ah, cool.
[23:23] <hatch> ahh - see I was thinking of using it as a filter not for polling
[23:24] <hatch> I've used it with a table with about 500 records before and it was very fast
[23:24] <hatch> but there comes a point where the overhead of the initial load is too much
[23:25] <hatch> here is an example http://yuilibrary.com/yui/docs/autocomplete/ac-filter.html
[23:25] <hazmat> hatch, revision 19 app/views/search.js
[23:26] <hazmat> hatch, btw qbzr is a really nice gui on all the bzr commands, recommended.
[23:26] <hatch> hmm I'll have to look into this qbzr
[23:27] <hatch> ahh I see how you did that
[23:27] <hazmat> have a good one.. i'm out for the day
[23:27] <hatch> you too cya!
[23:28] <Makyo> hazmat, ciao