[01:16] is there a known way around lint issue with 'event_caught.should.be.true;' ? just change it to an equal and move along? [01:23] event_caught.should.equal(true) [01:24] k, yea, changed up to that and moved along [13:26] bcsaller__, Makyo heads up: we need designer review for your landscape branches before landing. I'll give more details later today [13:28] gary_poster, hi [13:29] hey therve [13:29] gary_poster, I'm sorry I didn't follow on annotations testing. Where are you at? [13:30] therve, np. We have a branch ourselves to provide some testing data. We have all infrastructure ready in GUI and are just hooking up assets. I expect it will be all landed by tomorrow, at which point we will be done unless told otherwise. :-) [13:30] ok great [13:31] gary_poster, it will end up quickly in the charm store version I guess? [13:32] therve on our regular schedule it would be up sometime this coming Monday. We have a sprint next week so that schedule might be a little rocky. If you would like it in the charm store asap we can try to make a release end of this week. That probably would be reasonable anyway [13:33] gary_poster, that's ok. If you can just ping me when it's up there, we'll be able to test on our side end to end [13:34] therve, great! sounds perfect, will do [13:34] sweet thanks [13:34] thank you [13:39] morning all, anyone have some spare tmie for a review this today? https://codereview.appspot.com/7363055/ [13:42] gary_poster: FYI the watcher branch has landed [13:43] Morning rick_h_ . I think we should have a call with you, hatch, maybe bcsaller__ if he wants, and myself when they show up (should be in 20 minutes or so). charmbrowser should work in context of subapp and multi-dimensional url code. [13:44] pre-imp might be good plan for branches at the statr now [13:44] pre-imp with gui team [13:44] gary_poster: we have assets from the newer design so things don't match at all, we'd either need old style versions or new versions of the existing ones [13:44] gary_poster: yea, saw the subapp branches fly by. There was talk of one of us on your stand ups but not heard any updates on that [13:44] rogpeppe, awesome! [13:44] gary_poster: rgr. [13:44] rick_h_, I mentioned to sinzui that you all are completely welcome [13:45] bcsaller__, ack. Could you make a quick screenshot to show goodspud? [13:45] gary_poster: yea, he was going to check on the timing of your stand up and get back to us but haven't heard [13:45] gary_poster: am just playing around with proof-of-concept bottom-up stuff for the megawatcher [13:45] awesome rogpeppe . Did you see the novel I wrote for the spreadsheet? [13:45] gary_poster: but yea, would love to have a conversation and a chance to brain dump. [13:45] gary_poster: not sure i did actually [13:45] rick_h_, 10:30 EST, 1530 UTC [13:45] rogpeppe, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AoQnpJ43nBkJdEFIZVg0dnN0SXNNREpTMTd6X1FMS1E#gid=1 [13:46] gary_poster: ok cool good to know [13:47] gary_poster: i see what you mean by "novel" :-) [13:47] :-) [13:48] rogpeppe, if you have any concerns would be happy to talk/adjust [13:48] gary_poster: https://docs.google.com/a/canonical.com/file/d/0B4VD02DIPjvMRS02dzlKS1hlX2s [13:49] brb [13:49] bcsaller__, "Sorry, the file you have requested does not exist." [13:49] try sharing with me explicitly? [13:50] gary_poster: any chance it could be bullet pointed? (aside: i find the present tense style a little odd - it sounds like we already have some of this stuff; perhaps "make read-only GUI work with juju-core" might read better than "Read-only GUI works with juju-core". ignore this trivial suggestion at will! [13:51] rogpeppe I couldn't add any in-cell newlines. wil try again [13:52] gary_poster: hmm, maybe it's not possible. [13:52] gary_poster: maybe just 1) xxxx 2) yyyy, then [13:53] ok cool rogpeppe [14:00] rogpeppe, future tense and identifying numbers/letters added [14:00] morning [14:01] gary_poster: just making coffee then I'll be ready for a call [14:01] morning hatch. thanks [14:01] gary_poster: looks great, much easier to take in, thanks! [14:01] cool, thanks for review and suggestions [14:01] gary_poster: is https://docs.google.com/a/canonical.com/file/d/0B4VD02DIPjvMRS02dzlKS1hlX2s/edit better? [14:02] yes bcsaller__ thanks === bcsaller__ is now known as bcsaller [14:03] goodspud, hi. bcsaller points out that icons we've received for landscape integration are for the future, not the present--note icon size (and color?) of https://docs.google.com/a/canonical.com/file/d/0B4VD02DIPjvMRS02dzlKS1hlX2s/edit [14:03] bcsaller__: did you want me to make any changes to the subapp branch? https://codereview.appspot.com/7384059/ [14:03] goodspud, how would you like to proceed? [14:04] gary_poster, I'm just having a chat with Greg about it. Please hold caller... [14:04] hatch: If you made the previous changes it should be fine :) [14:04] thanks goodspud [14:06] gary_poster: ok ready [14:07] hatch, cool. rick_h_ hatch and bcsaller if he wants to (I'll call you in if we have a deep discussion of the URL namespace stuff) let's meet in the juju gui room [14:08] gary_poster: I can join in a minute, coffee is almost ready :) [14:08] heh ok [14:08] cool [14:12] gary_poster, bcsaller__ , Greg is going to provide you with icons at a reduced size. He based the updated designs on the specifications provided by Matt Chapman which weren't fully implemented anyway. So at some stage we'll have to update the pop-up menu.... unless we get rid of it completely for 13.10 (which is a possibility). [14:16] gary_poster, bcsaller__ . Greg is working on them now. The text shouldn't be blue though. Same colour/style as the text for other menu items. [14:21] gary_poster, bcsaller__ , updated icons are here: https://drive.google.com/a/canonical.com/#folders/0B1IM--9A1RkTUEpZN2h6cEwtVFk [14:21] thanks goodspud sorry on call [14:21] np [14:43] bcsaller, do you have enough info for landscape branch now? [14:43] gary_poster: looks that way, updating now, thanks [14:43] cool ty [14:50] frankban, approved FF testfix branch, ty. Don't see card (slack I guess?) but you can put me on tag if there is one [14:51] gary_poster, the card is down in slack, I put your tag on it [14:51] gary_poster: thanks [15:08] bcsaller: hey are you looking for reviews for 7381060? [15:10] hatch: yes, that would be helpful [15:10] ok anything special I need to do to view these new features ? [15:10] or just checkout and run [15:10] er....branch and run [15:10] * hatch smacks git out of head [15:11] hatch: oh, you need the special rapi-rollup branch for it to work, lp:~bcsaller/juju/delta-annotations/ [15:11] that should get merged soon, but for now. [15:11] I'll put it on the card [15:12] deal [15:13] it is however a pretty simple branch [15:19] yeah looks like it - how do I get the icons to show? [15:19] hatch: if you click on services in the env view some of them will be tagged (at random) in ways that make the new menu items appear. [15:22] * hatch doesn't belive you :P [15:22] tried sample and large [15:23] hatch: you're using improv from the delta-annotations branch? [15:23] that I am [15:25] sample starts with 15 units, there is a 33% chance of any unit being flagged with either of the annotations so the odds that none of them are flagged is... very low [15:25] ok let me restart them [15:26] hatch: you see the normal service menu but the new items don't appear or you're not sure where to look still? [15:26] hatch: on the improv console you can see the annotations in the outgoing delta stream as well, thats something to look for [15:26] view, build relation, destroy are the only ones that appear [15:29] jujugui in 30s? [15:32] I's comin [15:33] benji [15:33] coming [15:34] gary_poster: google+ browser plugin is broken; diagnosing [15:41] gary_poster: can you paste that here? [15:41] "designreview" [15:41] can't believe you fell for that [15:41] LOL [15:42] LGTU [15:50] benji, lots of hum noise when you open the mic [15:55] Shoot, bcsaller goodspud, did you want to do the review now? [15:55] Makyo, when you guys are ready [15:55] I ran away too fast. [15:55] Makyo, goodspud we can try the screen share now [15:55] goodspud, we're in jujugui [15:55] Coming! [16:42] here goes - attempting to work solely from my laptop [16:43] hatch: laptops ftw [16:43] laptops + dock for more win [16:43] yeah that won't happen with this laptop - it only has an HDMI port and my monitor is too high resolution [16:43] but I need to make sure I have everything for the sprint [16:44] hatch: ah, gotcha [16:44] yea, I'm always ready to get home to larger displays/real keyboards by the end of sprints [16:44] stretching 1920x1080 to 2560x1600 make it look REALLY bad heh [16:45] hah [16:46] I've already found I have no tunes on here....that's a serious issue [16:46] :P [16:47] heh, just downloaded all my Google music onto the laptop second drive yesterday myself [16:51] I also noticed that thunderbird has a lot of chrome [16:52] makes for very small views on a laptop :) [16:52] *cough* tilingWM *cough* [16:53] right now I have each app in it's own desktop [16:54] the top 1/5th of my monitor is still chrome :) [17:09] jujugui, does anyone happen to have a nexus 10? this is a work-related question :-) [17:10] gary_poster, nexus 7 in hand [17:10] n7 here as well [17:10] :) [17:11] good news - I changed the sub app code and my tests failed.....at least I know those are working :D lol [17:11] * benji considers several options for "does anyone happen to have _______? this is a work-related question" jokes. [17:11] I see what you did there... [17:11] cool hazmat and hatch, thanks. we need to support nexus 10 by April, at least at minimal demo level. We can check out the GUI on the n7 at the sprint and see how we are doing. [17:11] can I requisition one? ;) [17:12] yeah, I tried that already ;-) [17:12] yea, been hovering over the buy button since I saw the touch demos [17:12] gary_poster: nexus 10 running Android or Ubuntu? [17:12] benji, android I think [17:12] gary_poster, right now sorry they are out of stock in Canada so I can't even buy one [17:12] But Ubuntu would be cool [17:13] hmm, in stock here in play store :) [17:13] in that case testing on another tablet might give us a good start [17:13] abentley: has an android tablet, is it a 10"? [17:13] I have access to a Surface RT just FYI [17:14] I still have the touch improvements branch laying around. I dropped it when we said we were moving the touch story to 13.10, assuming it's back on track? [17:14] Makyo, we have demo requirements, that's it. Your touch improvements might be all we need [17:14] rick_h_: Yes, it's the original Asus Transformer, a TF101. [17:14] gary_poster, alright, will merge it with trunk and keep it on hand,then. [17:15] gary_poster, !!! Will merge trunk with it, sorry :S [17:15] cool Makyo thanks. :-) [17:15] abentley: does it run chrome for android? might work for a test case [17:15] rick_h_: Yes, it does. [17:15] gary_poster: ^ so that might work since N10 comes with chrome ootb anyway. Just be a performance diff [17:16] FYI, we were able to do some user testing of the "prototype" over the weekend at the SCALE conference (I don't actually know what that is). We get the feedback from our researcher on Monday. [17:16] rick_h_, cool, thanks. [17:16] goodspud, sounds great. Look forward to hearing [17:43] hey benji have you run tests for juju-core lately? i'm seeing 9 failures in trunk. [17:43] bac_: I have a couple of failures on my branch, but they are about openstack things that I probably don't have the right environment for testing anyway [17:44] I haven't updated my branch since yesterday though, so that might be part of it [17:45] benji: i'm getting these (from 'go test ' |grep FAIL) http://paste.ubuntu.com/5571126/ [17:45] bac_: nope, I haven't seen that. I can get a fresh trunk and try it, if that would help. [17:46] benji: if it isn't too much trouble [17:46] sure, one sec [17:53] gary_poster, bcsaller - just fyi final push of the app extension code was pushed - I was pretty sure you were both LGTM with changes but just making sure b4 I push [17:53] er submit [17:54] bac_: I get some failures, but they look environmental; as for the tests that fail for you, they pass for me: [17:54] ok launchpad.net/juju-core/worker/uniter 89.878s [17:54] ok [17:54] thanks! === bac_ is now known as bac [18:07] lunch & [19:00] I think we have a layout bug on trunk...when running I need to scroll up/down to see the whole app - it's a little bit more than the height of the footer too tall [19:01] I dont' see a min-height anywhere but I might be missing something obvious [19:01] hatch, there is a min height and width. [19:01] http://uistage.jujucharms.com:8080/ looks ok to me [19:02] height and width is controlled in environment IIRC [19:02] ahh it's not hardcoded into the css [19:02] gotcha [19:02] sort of, the env is scaled on viewport size change [19:02] * hatch goes back to work :) [19:31] benji: have you seen this: http://labix.org/cobzr -- the How It Works section you may find interesting [19:32] bac: heh, I had not [19:45] benji: if you wanted to do a non-binding review, my 'expose' branch is at https://codereview.appspot.com/7369058/ [19:46] i figure it is good for us to start doing reviews to gain exposure. you agree? [19:46] sounds good, I'll take a look [19:46] i did one today prefaced with "i'm not a juju-core reviewer, but..." [19:46] ...I play one on the interwebs [19:47] I'll start mine with "I don't always review juju-core code, but when I do...". [19:47] benji: i'm particularly interested in feedback on the issue with api_test.go we discussed, regarding the silly second test. [19:47] heh [19:47] k [20:09] wrt conflicts with bzr - is the workflow to head into the conflicted file, fix the merge, commit, and done? [20:09] same as git? [20:10] gary_poster: N10 acquired [20:10] rick_h_, woohoo! [20:10] lucky! [20:10] local walmart had it in stock, now I need a shower [20:10] clearly the play.google.ca UPS sled dogs are slow at this time of year [20:10] :) [20:10] hah [20:11] lol @ need a shower [20:11] have some new additons to `people of walmart` ? [20:12] According to this recruiter email (grrr Monster), I have the right mix of skills to be an "Independent Insurance Sales Agent." I guess that's a valid backup career... :P [20:13] Makyo, are those skills "sentient being" ? [20:13] ;) [20:14] hatch, I'm assuming so :) [20:15] haha [20:16] hmm bzr is saying i have conflicts but those files don't have any of the <<<<< [20:16] hatch, are there .THIS and .OTHER files? [20:16] negative [20:16] hatch, sorry, .THIS [20:17] still no - this came after lbox submit [20:17] so maybe they are in another branch [20:17] Oh, huh. [20:18] are they usually in a separate branch? [20:18] I don't see an lbox folder anywhere [20:18] and find doesn't find any THIS or OTHER files [20:19] first bzr conflict :) [20:20] hmm, so if it's in the lbox submit part then someone submitted something that lbox is breaking when trying to update to trunk [20:20] go back to your branch and do a fresh pull with trunk to see what's up [20:20] ok doing a pull on trunk [20:21] hatch: lbox submit creates a new branch in the parent directory and then erases it when done (though i would've thought it would keep it on error) [20:21] yeah that's what I thought although the branch doesn't stick around [20:22] so....what's the workflow for this ;) [20:22] bzr merge lp:juju-gui [20:22] manually resolve any conflicts [20:22] bzr resolved [FILES THAT YOU RESOLVED] [20:23] bzr commit -m 'merge with trunk' [20:23] or similar [20:23] ok so then my branch will have trunk in it [20:23] * bac hearts smerge.el [20:23] y [20:24] and then the proper way to push that to trunk? [20:24] merge mybranch into trunk and push? [20:24] lbox submit should work AFAIK [20:24] ahh ok [20:24] great lemme give that a go [20:24] bac: I finished my non-review of your branch. [20:24] benji: cool [20:34] running tests and builds on this laptop kills the battery heh [20:34] guess it isn't a huge fan of 100% CPU [20:34] :) [20:34] Makyo, out of curiosity was Nick happy with the design aspect of the bottom link work you are doing? [20:34] :-) [20:35] I wonder what it is about me that prefers noses for my smileys... [20:35] they are more personal [20:35] ...my older son might tell me it is because my own is rather large... [20:35] personal noses? [20:35] :-) [20:36] yeah look at that thing....it just says so much about that emoticons life [20:36] gary_poster, happy with the bottom links, unhappy with the other controls on the bottom of the service view. Expose and destroy were to be moved up to the top bar. He just got me assets this morning, though, so that's going in this branch to pass UX check. [20:36] And for what it's worth, I used to use :o) (and still do sometimes), until I got asked if it was a clown. Confidence: shattered. [20:36] lol [20:37] haha now I can't unsee that as a clown [20:37] damn [20:37] cool about Nick, thanks Makyo [20:37] RIGHT? I will never not be a clown :( [20:37] LOL [20:38] hahaha [20:38] poor you [20:38] :'o( sad clown [20:38] Sometimes the nose just adds too much width. [20:39] Like the Charlie Brown face :S That 'S' is too wide already. [20:39] The Design and Aesthetics of Emoticons, by Jujugui [20:40] amazon best seller right there! [20:41] there's always \u1F443 (http://www.fileformat.info/info/unicode/char/1f443/browsertest.htm) [20:43] :-) [20:43] Me, I'm a fan of http://www.fileformat.info/info/unicode/char/1f63c/index.htm [20:54] hmm it looks like the merge chose the trunk over some of the changes in app.js [20:54] does that happen often? [20:57] oooooor [20:57] I screwed something up.....the more likely case [20:57] :) [21:23] bcsaller, gary_poster when you guys have a moment could you please check out the updated app extension branch https://codereview.appspot.com/7381055 [21:23] I somehow missed the code which called the callbacks in the proper context [21:23] :/ [21:24] hatch, whassup? That one is submitted? ok looking for diff from submission... [21:24] Set 11 on that link [21:24] right [21:25] it was missed because technically it's the router code - my bad [21:26] hatch, charmbrowser was originally supposed to be default url namespace--the name doesn't matter but the idea was that existing charm browser urls, like http://jujucharms.com/~juju-gui/precise/juju-gui, would still resolve correctly in the charm browser sub app. It looks like you assume that root is *not* a subapp [21:27] hatch: you should do this as another branch if the other is submitted already. Also this code isn't correct, router has a .defaultNamespace which isn't 'root' as you suggest. Additionally the callback is triggered with .call below and is passed self. This could be a var which is the subapp or self depending on where we found the callback [21:28] not only would existing urls resolve correctly, but the urls for the charm browser would be attractive when you started in the full charm browser experience [21:29] hmm, can we chat about this? [21:29] bcsaller, I think he changed the defaultNamespace by changing the instantiaton of the router, yeah? [21:29] hatch, who, me? :-) [21:29] you and bcsaller :) [21:29] because I must have totally misunderstood something [21:29] ok [21:30] to the juju gui cave [21:30] kinda like bat cave, y'know [21:30] gary_poster: he did which is an issue, but you wouldn't encode that string both places, you'd still use the attr assigned when you init the object if that type of check was what you wanted [21:30] bcsaller, ah gotcha [21:31] bcsaller, are you coming? [21:31] into the call? [21:32] hatch: var callingContext = subapp[callback] ? subapp : self; callback.call(callingContext, ...) [21:58] var callingContext = subApp && subApp[callback] ? subApp : self [22:27] bcsaller, just before I commit this i want to make sure I'm on the same page again :) https://gist.github.com/hatched/d2ea9b39964c477b924e [22:29] hatch: yes and then passing callingContext as callback.call(callingContext, ...) [22:29] yeah sorry - didn't include that part in the paste [22:29] ok perfect, and it appears to work properly [22:29] :P [22:29] sorry about that - I didn't really understand the direction we were going with that stuff [22:31] hatch: no prob :) [22:33] Dogwalkination. [22:33] enjoy! [22:35] hmm almost forgot tests! [22:35] although..... it looks like the current tests might cover this change [22:36] nope [22:36] need one more [23:39] hm, att uverse router appears to be dying