/srv/irclogs.ubuntu.com/2014/08/01/#juju-gui.txt

huwshimihatch: Also, if you have any ideas on how to test the expose option exist in the new "ghost" inspector I'd love some help with that00:05
huwshimihttps://github.com/juju/juju-gui/pull/46100:05
huwshimi(see the last commit)00:05
hatchlooking00:06
hatchdon't like partials I see :)00:06
huwshimihatch: Oh, no, it's just it only gets included in one place now00:06
hatchhuwshimi well you can only test that the class is there00:07
hatchnot that it's actually doing what it is supposed to be doing00:07
huwshimihatch: My problem is that I don't actually know how to put the inspector into "ghost" mode. Then 'pending' variable doesn't actually do anything: https://github.com/juju/juju-gui/pull/461/files#diff-f05fb78d550f50174f5355a05130fa02R74200:12
hatchhuwshimi sorry my computer decided it didn't like my keyboard anylonger00:15
huwshimi:)00:15
hatchhmm that should work00:16
hatchhuwshimi oh the mix command is wrong00:17
hatchhuwshimi https://gist.github.com/hatched/b8b2d12bb6d4c6ad90a800:17
hatchthis goes around line 90 of test_inspector_overview00:18
hatchto replace what's there00:18
huwshimihatch: Ah great, I'll try that in a minute!00:18
huwshimiMakyo: Are you around?00:31
huwshimiMakyo: Just wondering if you actually started your card, I have inadvertently fixed it in the branch I'm working on...00:34
huwshimihatch: This branch is ready for review now too: https://github.com/juju/juju-gui/pull/46700:35
hatchcool ill take a look00:36
hatchmaybe....if my internet stays up00:36
hatchoh huwshimi  we now don't rebase until just before landing00:37
hatchso reviewers can see the changes 00:37
hatchlike you can rebase before putting up for a PR00:37
hatchjust don't rebase between PR and landing until just before landing00:37
rick_h__hatch: https://twitter.com/rwjblue/status/49499227123510067200:38
huwshimihatch: Sure, makes sense00:38
hatchrick_h__ w000000t00:39
rick_h__hatch: ember? for a blog? seems a bit extreme00:39
rick_h__hatch: and upgrade time00:39
hatchthe admin panel00:39
huwshimihatch: In that pr I just sent you I fixed Matt's card he is in 'Branch start' should I steal that card off him?00:39
jrwrenwordpress is extreme for a blog too :)00:40
hatchI'm not going to upgrade the charm to include the RC00:40
hatchbut this ight be time to provide the option to pull in the source from elsewhere00:40
hatchhuwshimi yes, and send him an email just to be safe :)00:40
huwshimihatch: Sure!00:40
hatchhuwshimi shipppppit00:44
huwshimihatch: Cheers mate00:44
hatchrick_h__ can you put some input on what should be happening here https://bugs.launchpad.net/juju-gui/+bug/1351112 I think that it should add the unplaced unit back into the unplaced unit list.....buuuuuuut00:46
huwshimihatch: So with that new mix line should I just pass the 'pending' as I have done?00:47
_mup_Bug #1351112: Deleting an ecs'd machine with placed service still shows service in change list <juju-gui:New> <https://launchpad.net/bugs/1351112>00:47
hatchhuwshimi yep00:47
rick_h__hatch: looking00:47
rick_h__hatch: remind me to look tomorrow00:49
rick_h__hatch: brain is slow and trying to qa kadams54's stuff and no more capacity00:49
hatchhaha - too much thinking?00:49
hatch:)00:49
jrwrenupdated: https://github.com/CanonicalLtd/charmstore-charm/pull/100:51
jrwrenits practically all new.00:51
jrwrenoops, private.00:52
huwshimijrwren: Hello, welcome!00:56
hatchjrwren putting in some OT?00:59
hatch:)00:59
jrwrenhi huwshimi, thanks for the welcome. good to be here.01:02
jrwrenhatch: yes, I guess so.01:02
jrwrenYou know how it is when you just really want to get something done :)01:02
huwshimijrwren: Great, things going well so far?01:03
jrwrengood enough.01:03
hatchyup I do01:03
jrwrenI'm funding bugs and warts and stuff. :)01:03
jrwrenAnd I'm learning tons. I'm still very new to pretty much everything.01:04
huwshimijrwren: Yeah, lots to learn01:04
hatchjrwren yeah after a couple months you'll be right in the swing of things01:26
hatchhuwshimi be sure to update the board when your stuff lands01:31
huwshimihatch: Into daily call?01:31
hatchyep01:31
huwshiminp01:31
huwshimihatch: When I set pending to true it doesn't render the UI, any obvious ideas?01:53
huwshimiActually I think it's rendering the old ghost inspector02:02
hatchoh u need to se the mv flag02:21
hatchset02:21
hatchhuwshimi02:21
huwshimihatch: Yeah, I have!02:26
huwshimi(well, in my local branch)02:26
hatchhmm02:26
hatchare you setting it before calling the setupInspector?02:27
huwshimiyep02:27
hatchwell I have noooo idea02:27
hatchyou'll have to step through it I guess02:27
huwshimihatch: it's hitting this here: https://github.com/juju/juju-gui/blob/develop/app/views/environment.js#L9702:28
hatchOHHHH02:29
hatchok that's why it's not working02:29
hatchsec02:30
hatchhuwshimi so under mv we no longer hit that in the real code flow we now use the dispatcher https://github.com/juju/juju-gui/blob/develop/app/subapps/browser/browser.js#L58602:31
huwshimihatch: OK, so any ideas how I get it to call that instead?02:32
hatchhuwshimi well I can't believe we haven't tested any of this stuff being passed a ghost model yet02:33
huwshimihatch: Isn't this what you and jcsackett did in London?02:34
hatchnope this was done pre-london02:34
hatchI think by jc though02:34
huwshimioh ok02:34
huwshimihatch: pending must be set at a later point than where I'm doing  it if this works not in the test02:39
hatchno that area is never called in a real app02:39
hatchunder mv02:39
hatchit is instantiated in the browser.js file02:39
huwshimisure, but setting pending is what is making me hit this02:43
hatchyeah so that's not going to work02:49
hatchlike we are hitting a branch of code that's going to be going bye bye once mv hits02:49
huwshimiyeah02:51
huwshimihatch: Any brilliant ideas or should I head to lunch?03:00
hatchhuwshimi the only thing I can think of is to instantiate the view manually 03:00
hatchthe overview view03:00
huwshimihatch: OK, I'll try that03:01
hatchbut maybe dig in the closed PR's for when this stuff landed03:01
hatchmaybe use git blame to find it03:01
hatchbecause we must have added tests around this stuff03:01
huwshimisure03:06
rogpeppeurulama: mornin'06:28
urulamarogpeppe: morning06:35
huwshimirogpeppe, urulama: morning06:41
rogpeppehuwshimi: hiya06:41
urulamahey there, huwshimi06:48
rogpeppeurulama: the reason we don't use errgo.Any everywhere is that we want to have control over the error codes that are being generated (and that can be relied on)06:53
rogpeppeurulama: the place to use errgo.Any is where there's a callback that we want to give control over the error codes06:53
rogpeppeurulama: a classical example being when we have a general handler that has more specific handlers plug into it06:54
rogpeppeurulama: in general, my view is that use of errgo.Any is to be avoided when possible. i am aware that this view has been the source of some contention in the past :-)06:55
urulamarogpeppe: yeah, that errgo.Any is funny :)06:57
urulamarogpeppe: ok, could we have a comment then for us non-errgo-experts, to know the reasoning ... just as a reminder not really comment on each Any call06:58
rogpeppeurulama: the motivation comes from experience with large systems where there can be a lot of "action-at-a-distance" where something high up relies on specific error codes generated by something much lower level.06:59
rogpeppeurulama: yes, that's a good idea. will do.06:59
urulamarogpeppe: the comment would be exactly what you've written in the reply on the PR07:04
rogpeppeurulama: the "see at a glance" comment?07:05
urulamaBecause we don't want parseURL setting status codes. By omitting errgo.Any, we can see at a glance which are the possible places that could be returning an error with a Cause (the only kind of error that can end up setting an HTTP status code)07:06
rogpeppeurulama: oops, just realised there was a file missing from my commit. i've just re-pushed (the file is params/error.go)07:10
urulamarogpeppe: that's a problem with reviews on github ... it's PITA to see the whole code and then one just assumes that "it's there from before" :( 07:12
urulamarogpeppe: regarding our morning call ... it's way too loud today at home, i'll have to move to another location07:30
rogpeppeurulama: ok. let us know when.07:30
* urulama brunches09:22
rogpeppetrivial PR: https://github.com/juju/charm/pull/3209:25
* rogpeppe grabs breakfast09:25
rogpeppeurulama: i've made all those changes requested, i think (and having a clear policy now made it easy to find a couple more places where I omitted an errgo.Any) https://github.com/juju/charmstore/pull/5010:09
urulamarogpeppe: looking10:17
rogpeppeurulama: it's a pity that github doesn't make it easy to see what changes have been made since the last review comments were made10:17
urulamaindeed10:18
urulamarogpeppe: thanks for the comments, i think that the code is much easier to read now. 10:22
rogpeppeurulama: great, thanks10:22
rogpeppefrankban, urulama, jrwren: fairly trivial fix to charm.v3: https://github.com/juju/charm/pull/3310:35
rogpeppereview appreciated, because this is blocking the "user charm.v3" branch from landing10:37
urulamarogpeppe: looking, see that you got lgtm from core for #32 and #31 as well ... nice10:39
urulamarogpeppe: package version independent code :D10:49
* frankban lunches11:05
rogpeppebac, jrwren, frankban: i need a second review of this, please, before i can land it: https://github.com/juju/charmstore/pull/5011:16
rick_h__morning all11:23
urulamamorning, rick_h__11:23
jrwrenmorning all12:04
urulamamorning jrwren12:13
urulamajrwren: just a quick notice to pay attention on the details of error handling in that PR #50 as we'll use that on all services (until replaced by something more new and shiny) ... if you haven't already that is12:18
* rick_h__ heads to the coffee shop for morning work12:18
jrwrenurulama: ok, thanks.12:18
rogpeppejrwren: hiysa12:30
rogpeppejrwren: hiya, even12:30
rogpeppejrwren: any chance you could review that branch too, please, as i can't land it without 2 reviews12:30
rogpeppe?12:30
jrwrenI thought I did.12:31
frankbanrogpeppe: review done12:31
rogpeppejrwren: ah, perhaps i just didn't refresh the page12:31
rogpeppejrwren, frankban: thanks!12:32
rick_h__jrwren: make sure to leave a final 'comment' to help indicate the review is complete. (didn't look if you did there but just general fyi)12:32
kadams54guihelp: yesterday I realized that the error message I was seeing was not the same as the one I was supposed to be seeing. I setup a trusty machine and was trying to deploy precise charms.12:33
kadams54I think there have been discussions about this in the past, but are there any plans to filter charms based on series?12:34
kadams54Also: should I setup my ec2 as precise for the time being?12:34
rick_h__kadams54: is this in reference to your current card?12:35
kadams54Yeah12:35
rick_h__kadams54: frankban landed some work this week that has machine auto match the right 'series' based on what's placed on them12:35
rick_h__kadams54: so there might be some other work effecting what you see atm12:35
rick_h__kadams54: hmm, so what error are you seeing now? 12:36
rick_h__kadams54: This might work now with frankban's changes actually12:36
kadams54"Series does not match"12:36
* rick_h__ goes to get the bug12:36
kadams54I checked the core codebase and it throws that when the unit's series does not match the machines12:36
kadams54So yeah, frankban's work might have helped keep me from shooting my foot off :-)12:36
rick_h__kadams54: ok, so you're getting that error out of core12:37
rick_h__?12:37
kadams54Yes12:37
kadams54GUI tries to deploy the unit to the container and gets an error… which it should, according to the card.12:37
kadams54I just didn't realize initially that the error I was getting back was the wrong one.12:37
kadams54So even though I'm working in the GUI, the error is coming from core12:38
rick_h__kadams54: ok, so the bug is that the error is machine doesn't exist, but that's "fixed" and what you're seeing is the wrong series error instead now12:38
rick_h__kadams54: hangout please? I want to make 100% sure of the steps and such12:39
kadams54I'm not sure if it's "fixed" or if I was just hitting the "wrong series" error first.12:39
kadams54If it is fixed, I didn't do anything to fix it :-)12:39
kadams54Sure12:39
kadams54Standup hangout?12:40
rick_h__kadams54: sorry, the friday one12:41
bacgah, no rain here for six weeks and the tropical storm is due to arrive about the time i have to go to the airport tomorrow.12:43
rogpeppebac: ha, no rain here for ages either, and the downpours are just starting in time for a nice weekend out camping12:51
bacrogpeppe: they aren't so good at periodic maintenance here.  the slightest rain causes the highway to flood since the stormwater system is clogged up.  makes getting to the airport hard.12:53
rogpeppebac: well at least we don't have that problem... unless it *really* rains12:54
bacyes, because you're not 1 GDP in debt12:54
bac:(12:54
rick_h__kadams54: pr #171 can land correct?12:55
jrwrenbac: Where does it flood?12:56
bacjrwren: mainly the roadways.  and parking lots. and low lying areas.  not our house, though.12:57
jrwrenWe have some of that here, but only on a few select roads.12:57
* urulama sees the Sun for the first time since London ... happy to switch with people with no rain ;)12:57
rick_h__jcsackett: kadams54 are either of you up for reviewing/qa'ing frankban's branch please? https://github.com/juju/juju-gui/pull/46913:11
jcsackettrick_h__: i thought frankban had another commit he wanted to push up to that branch?13:12
jcsacketti've been holding off waiting for changes; did i misunderstand?13:12
frankbanjcsackett: the branch is ready to be reviewd13:13
jcsackettdig, well i'm sorry for holding it up. :p13:13
* jcsackett goes to review it.13:13
frankbanjcsackett: np and thanks13:13
bachatch: did your ac branch land?13:18
hatchbac last I checked I needed one more review13:19
bacoh13:19
bacok13:19
rick_h__hatch: I reviewd it this morning13:19
rick_h__hatch: one point in there please13:19
hatchohh ok13:19
hatchwill look13:19
hatchsorry there is like 200 emails, haven't gotten through themall yet13:19
hatchheh13:19
rick_h__heh, np. Figured it was early for you yet13:19
hatchrick_h__ replied13:20
hatchyeah it's still only 7:2013:21
hatchtrying to buy a kite on ebay so had to get up early to check on it haha13:21
hatcher get online early13:21
rick_h__hah13:21
rick_h__hatch: ty13:22
hatchanyone here use duolingo?13:24
bachatch: i did for a while.  plan to start again13:33
rogpeppehatch: i thought about it recently, but didn't13:33
bachatch: it is really good13:33
rogpeppehatch: i know some friends that are really into it13:33
hatchI just started on Spanish, prepping for a winter getaway (if we can ever get our S$%^ together) :)13:33
jcsackettso, "e", "ev", "evt" for events? i see all three, and i see many diffs that switch them back and forth. can we just pick one? :p13:34
hatchafter one lesson I've already learnt more than I did before heh13:34
hatchjcsackett I vote for e (ev is from benji, evt is from frankban) 13:34
hatchlol13:34
frankban:-)13:34
jcsackett"evt" however gets "<3" from the boss man. :p13:34
frankbanhatch: evt is because I want t make you happy: I'd write that as "event" ;-)13:35
jcsacketthatch: my pr is updated btw.13:35
hatchhaha13:35
bachatch: duolingo produces some silly things to say:  'the duck drinks milk'13:36
rick_h__single letter var names are evil no matter what :P13:36
rick_h__evt reads nice to me and love s/e/evt13:36
bachow many letters have we saved, if you include this discussion?13:36
rick_h__but it's personal preference. I think ev was me caving to hatch. 13:36
rick_h__bac: 3, it's a fact13:36
rick_h__:) 13:36
* jcsackett laughs13:36
hatchlol13:36
jcsackettdo we have actual style guidelines written anywhere for jujugui? or is it just "whatever the reviewer and lint will let through"?13:37
rick_h__come on, the linter hates on the rest of my party, have to find the points to chat about somewhere13:37
rick_h__jcsackett: no, I don't know we'd ever get everything through a process13:37
hatchlol13:37
bacyeah, let's do that some friday i'm gone13:37
rick_h__I've still resisted the urge to one weekend s/  /    /g13:37
hatchwe still can't agree on doc formatting13:37
bac(or at least after lunch)13:38
rick_h__lol13:38
hatchSpanish is a wako language though bac, there is a male/female/adult/child version of everything13:38
hatchand they say English is hard13:38
bachatch: yeah, uh, i've noticed that.13:38
hatchhaha 13:38
bacno, English is insane.  gendered languages are stupid but English is insane if you're not 313:39
hatchthere their they're 13:40
baci have a theory computer scientists have a harder time learning a natural language since the inconsistencies are so aesthetically offensive.13:40
hatchhahaha13:40
urulamahatch: most eu languages are gender specific, we also have the third option, for "it" :D13:40
frankbanEnglish grammar is simpler than other languages, pronunciation is hard, due to the fact English is not a phonetic language13:40
kadams54rick_h__: pr#171? You mean #471? That's the one that hasn't been QA'd yet…13:41
urulamahatch: and not just singular and plural forms, but also special dual form ... 13:41
rick_h__kadams54: ah gotcha13:42
jrwrensurely there is a list of things you DO agree on which could be written.13:42
rick_h__kadams54: did you find out how you did it locally?13:42
hatchurulama haha damn....13:42
kadams54rick_h__: no, I got distracted… looking now.13:42
rick_h__jrwren: I thin kit's that code is good13:42
rick_h__jrwren: that's about it13:42
urulamahatch: so, try learning German (or slavic languages), then you'll consider Spanish simple :D 13:42
rick_h__jrwren: so much history...I'm actually kind of floored that I asked teo join this team. The first 6mo was so rough. 13:42
jrwrenrick_h__: lol13:43
hatchurulama well I know some Ukranian does that count?13:43
jrwrenrick_h__: how long has it been?13:43
rick_h__jrwren: hmm, 1.5yr on this work? 13:43
rick_h__the GUI stuff13:43
rick_h__I remember after christmas working on charmworld/charm browsing in the GUI13:43
urulamahatch: :)13:43
rick_h__so little over13:43
hatchjrwren no we don't agree, we just tolerate...13:44
hatchit's like a supersaturate 13:44
jrwrenso sad.13:44
hatchone of these days it's gona explode into extra comment styles and single char variables everywhere13:45
* jcsackett one day will work through the holidays to re format everything, update the linter, land a style guide, and pronounce it the law of the codebase...13:45
jrwrensounded like flake8 was agreed upon.13:45
rick_h__at some point you realize there's natural things that are purely opinion and try to do the best you can13:45
jcsackettpython is easier to agree on.13:45
jcsackettjavascript is a mess to begin with, so... :p13:45
rick_h__the python 'everyone agrees' is a lie13:46
jrwrenGTK13:46
hatchlol13:46
rick_h__there's tools that half the people don't follow, the 'I pep8'd everything for you' pull request is a flame war in the making13:46
hatchhaha13:46
rick_h__and then there's always the old fallback of "if the stdlib doesn't even follow..."13:46
jcsackettrick_h__: never said everyone agrees, just that it's easier.13:47
* rick_h__ notes that as the guy that asked jrwren to add a make target to the charm linting the python13:47
rick_h__but that's for another channel13:47
jrwreni've always liked the policy that new code landing should follow the style guidelines, but you don't ONLY change style for style sake.13:47
* rick_h__ heads home from coffee shop, afk for a couple of min13:48
frankbanas a side note, the js linter we use sometimes goes crazy, e.g.: wrong indentation, this must be indented at 6, 9, 12.7 or 42 spaces... and I don't remember why we decided not to just indent everything with 2 spaces...13:49
jcsackettfrankban: +1 on your PR, QA OK.13:50
frankbanjcsackett: cool thanks13:50
jcsackettfrankban: i think when you can't find a logic to a style decision in GUI, the answer is there was no logic to it. :p13:50
jcsackettjujugui: i need one more review for https://github.com/juju/juju-gui/pull/470 (hatch, you had a chance to look at the update?)13:51
jcsackettjujugui: also, because my juju install is borked, kadams54 needs a QA on https://github.com/juju/juju-gui/pull/471 (it requires a live env)13:52
kadams54jcsackett: yeah, rick_h__ volunteered but I need to find more QA info for him.13:53
jcsackettkadams54: ah, cool.13:54
kadams54jcsackett: out of curiosity, do you know the value you passed in as source when you were trying to QA that PR?13:58
jcsackettkadams54: "repo branch-name"14:00
jcsacketti've since had juju refuse to connect to any of my deployments for my hackerspace--not sure if they're related, but i've got a todo to reset my juju stuff sometime today.14:02
jcsacketti've never cleaned up various ppas etc since i was on qa--figure there's a chance i'm working with bad stuff.14:02
jcsackettkadams54: not literally "repo branch-name", of course--whatever copied from github for your repo and branch name. :p14:03
kadams54jcsackett: Yeah, rick_h__ was having problems too…14:04
jcsacketthuh.14:04
rogpeppeurulama, frankban, jrwren: here's the stats Store code imported from the old charm store: https://github.com/juju/charmstore/pull/5114:04
jcsackett...wonder if the two things are unrelated, and the gui charm is having issues...14:04
* rogpeppe loves it when code is that modular14:04
jrwrenits a good sign.14:06
kadams54rick_h__, jcsackett: just figured out why I wasn't finding anything in my shell history… I hacked up fakebackend.js to return errors so I could dev locally. (Which was when I asked about updating it to do some of the same error checking as the real thing.)14:12
rick_h__kadams54: ah, cheater14:12
kadams54Yup.14:12
kadams54So… still no closer to understanding why the gui charm isn't getting pointed to the right source.14:13
rick_h__kadams54: yea, now that it's morning I'll try again and see what's up14:13
rick_h__sorry for the delays14:14
frankbanjcsackett, rick_h__: do we really want to collapse var declarations when the definition is "simple"?14:15
rick_h__frankban: it was agreed long ago that if they were simple one liners then it was ok to do14:15
rick_h__frankban: and anything multi-line, objects, arrays, etc would be split out14:16
frankbanrick_h__: I know it's ok to do that, I am not sure if it's optional or not14:16
rick_h__frankban: I take it as optional14:16
rick_h__frankban: the only time I call out is like hatch's when he had more than one var per line14:16
rick_h__as that hides potential vars14:16
frankbanrick_h__: cool thanks, are you QAing my branch?14:18
rick_h__frankban: no, left that for jcsackett 14:18
frankbanrick_h__: cool, he did it, thanks, will submit soon14:19
rick_h__frankban: ty much14:19
rick_h__frankban: bac didn't we update the charm for the KeyError: u'NetworkScope' issue?14:21
frankbanrick_h__: we updated quickstart, not the charm. Is the charm affected?14:22
rick_h__frankban: oh, maybe I've not updated quickstart /me goes to dbl check source14:22
rick_h__hatch: buld failed email?14:30
hatchyup got it re-running14:32
rick_h__kadams54: hmm, no idea why this is failing. The apt-get install runs and then it gets to Processing triggers for libc-bin ...14:34
rick_h__ldconfig deferred processing now taking place14:34
rick_h__and then it hangs and config goes into a bad state14:34
rick_h__before it ever hits git14:34
Makyojujugui call in 314:57
rick_h__kadams54: oh crap, all my issues were because I missed the s in your github username. 14:58
kadams54hahahaha14:58
rick_h__found where it logs out to, not the charm log :( but the all log14:59
rick_h__anyway, finally getting somewhere with your qa, thanks for your patience14:59
kadams54"I must've put a decimal point in the wrong place or something. shit, I always do that. I always mess up some mundane detail."14:59
bachatch that's a great look.  doesn't look dorky at all.15:00
rick_h__jcsackett: ^15:01
hatchbac? whowhatinthewhatnow?15:01
bachatch: :)15:01
bacPR just cut back from 19 to 15 holidays, starting next year.  (i don't get them)15:12
kadams54rick_h__: OK, I'm getting the right error now for my card, so venturing forth…15:20
rick_h__kadams54: woot15:20
rogpeppefrankban: i'm off in 40 mins, BTW. 't'would be great if you could perhaps have a look at that PR before then, please. ta!15:20
rick_h__ish15:20
frankbanrogpeppe: sure15:21
rogpeppefrankban: thanks15:21
bacrick_h__, rogpeppe, frankban: are we using github for the bug tracker for juju/charmstore ?  i see two issues are there.  jrwren has documented it as a TBD so i'm curious.15:21
rick_h__curses! out of tape15:21
rick_h__bac: yes, I think we should.15:21
rick_h__bac: since we don't have a LP fallback project15:22
rogpeppebac: i think so, yes15:22
hatchhmm internet isn't being too awesome today15:22
rick_h__bac: but I think we did have issues in LP in core we might need to peek at15:22
rogpeppebac: i prefer associating the bugs directly with the repo, tbh15:22
bacrogpeppe: what do you mean?15:22
rogpeppebac: well, since we're hosting on github, it makes sense to track bugs there, i think15:23
bacrogpeppe: ok, agreed15:23
rogpepperick_h__: those bugs would be more appropriately raised against github.com/juju/charm though, i think15:24
rick_h__rogpeppe: ok15:25
frankbanrogpeppe: so, is your branch just moving stuff from _old?15:25
rogpeppefrankban: yes15:25
rogpeppefrankban: with a few tweaks to fit the old stuff with the new15:25
rogpeppefrankban: (e.g. session becomes db)15:26
rogpeppefrankban: i haven't changed any of the actual logic15:26
frankbanrogpeppe: ok15:26
rick_h__kadams54: I think we fixed the error that you were working around and so QA isn't valid atm15:29
rick_h__kadams54: but the change is small, I +1 to land15:29
frankbanrogpeppe: LGTM15:37
rogpeppefrankban: ta!15:37
urulamarogpeppe: by "i haven't changed any of the actual logic" you mean that it's original form is good enough to be just easily hooked with handlers?15:43
urulamas/it's/its15:43
rogpeppeurulama: yes15:43
rogpeppeurulama: and there's already a handler in the old code that implements the actual stats/counter serving logic15:44
rogpeppeurulama: which is what i'm porting over currently15:44
frankbanguihelp: I need reviews/QA for https://github.com/juju/juju-gui/pull/473 ? Anyone? thanks!15:44
urulamarogpeppe: and the code covers /stats/counter use-cases? does it do more as well? 15:46
rogpeppeurulama: i don't think so, but /stats/counter is fairly general15:47
hatchfrankban on it15:47
frankbanhatch: thanks15:48
hatchfrankban so machines and containers use the same model?15:48
frankbanhatch: yes15:49
hatchfrankban how did you find this out? trial and error? Or is it documented somewhere?15:49
hatchthe MANAGE_ENVIRON15:49
hatchoh constants.go ?15:50
frankbanhatch: I don't know if it's documented, I saw that while implementing the mega-watcher for machines15:50
hatchohhh ok cool15:50
frankbanhatch: so server side15:50
frankbanhatch: I knew that sooner or later that jobs attr would be useful ;-)15:51
hatchhaha truth!15:52
urulamajujugui have a great weekend and may the gods of CI be on your side next week15:56
frankbanurulama: :-) and you, have a good trip15:57
kadams54rick_h__: What changed to fix the error?15:58
kadams54rick_h__: Maybe I should clarify… which error? As far as I know, there's still an error state that occurs when deploying to a ghost container. You'd mentioned earlier that frankban landed work that would fix deploying the series mismatch between charm and machine…16:00
kadams54rick_h__: just trying to figure out if I should continue working on the ghost container error.16:00
rick_h__kadams54: the only error I hit was an install hook failed on mysql16:00
kadams54And you were deploying mysql to a ghosted container?16:00
rick_h__kadams54: I did "Drag and drop the unplaced unit on the bare metal container."16:01
rick_h__which was a ghost, yes16:02
kadams54Hmm.16:02
rick_h__I then did the deploy, and the mysql install hook failed, but that was it16:02
kadams54OK, sounds like my current card may already be fixed then.16:02
rick_h__kadams54: so to deploy to a live env and switch up the source I just used juju-quickstart so the gui came up fast16:03
rick_h__kadams54: and then did juju set juju-gui juju-gui-source="https://github.com/kadams54/juju-gui.git services-without-machines"16:03
rick_h__kadams54: so you can also just set it to 'develop' to check current trunk16:03
kadams54Yeah, will do, thanks16:03
rick_h__kadams54: but yes, please verify the bug/card16:03
kadams54Definitely16:04
kadams54OK, lunching time16:04
frankbanhatch: re "state service": I just followed directions from luca: see bug 134867316:10
frankbanmup you won't be missed16:11
frankbanhatch: https://bugs.launchpad.net/juju-gui/+bug/134867316:11
hatchfrankban sure np16:11
hatchthx16:11
frankbanhatch: FWIW I agree with you16:12
hatch:) 16:12
hatchdoing qa, it'll take a bit to spin up an ec2 instance just fyi16:12
hatchI have issues with a LXC right now unfortunately and haven't had time to fix/investigate16:13
frankbanhatch: thanks16:13
frankbanjcsackett, jrwren: do any of you have time for a second review (no QA) for https://github.com/juju/juju-gui/pull/473 ?16:13
jcsackettfrankban: sure.16:14
jcsacketthatch: see? not just me with lxc issues. :p16:14
frankbanthanks16:14
hatchjcsackett I'm running in a vm making more vm's - it's like vm inception here16:15
hatchlol16:15
jcsacketthatch: i'm not sure if that's awesome or awful. :)16:15
hatchI blame us for not dedicating resources to get Ubuntu running perfect on Apple hardware lol16:15
bachatch: we should've all pitched in and bought a MBP for pitti, one of very productive ubuntu guys.16:19
hatchnot gona lie that's probably a good idea lol16:19
hatchI'd put in $100 to get the darn camera working16:19
hatchlol16:19
* rogpeppe is done for the week16:22
rogpeppehappy weekends all16:22
jcsackettand to you, rogpeppe.16:27
hatchcya rogpeppe  enjoy16:28
hatchfrankban so I've got the GUI up and running now16:35
hatchthe "State service" is listed on the machine, but nothing on the container16:36
hatchdoes that make sense? Should it also not be on the bare metal container?16:36
frankbanhatch: it makes sense if it's only on the machine IMHO16:37
hatchthe state service isn't in the root container?16:37
hatchI know you're just following UX, this is more of a discussion :)16:37
frankbanhatch: jujud runs everywhere. What I think we are trying to communicate is which machine is a state server16:38
hatchand that's not related in any way to the root container?16:38
frankbanhatch: I think the root container is a UI abstraction, from juju perspective the root container of machine X is machine X16:39
hatchyeah good call16:39
frankbanhatch: we have machines and containers in the GUI, but in reality the relations is between nodes in a tree16:40
rick_h__just a +1 to frankban there. The goal is to point out 2 things 16:40
rick_h__1. "why do I have a machine? I've not deployed anything yet."16:40
rick_h__2. "If you put stuff on this machine beware"16:40
rick_h__and I guess #3 "We're not going to let you remove this machine, it's a state server"16:41
frankbanrick_h__: I think also 3. I want to know if this environment is HA16:41
hatchyeah that sounds good16:41
hatchrick_h__ frankban  it has the trash can still16:41
hatch^ should that be fixed in this branch?16:41
frankbanhatch: I don't think so, and in an HA env it's still ok to remove a state server if required16:42
rick_h__hatch: I'd note it for follow up. It's under that big 'MV let's you do things you can't/shouldn't16:42
hatchok I'll add a note to the PR16:43
frankbanhatch: thanks16:43
hatchok commented, do with it what you will :)16:43
* rick_h__ goes to make up some lunch16:44
hatchMakyo the bug #1350505 I know there are supposed to be a relation button but I can't get it to actually render17:14
_mup_Bug #1350505: Relation inspector does not have actions attached properly <juju-gui:New> <https://launchpad.net/bugs/1350505>17:14
hatchis there a trick or have I stumbled uppon another issue?17:14
hatchohh right they only pop up when there is a relation error17:15
hatchdeleting a relation using the popup when clicking the relation line doesn't ask you to confirm deleting the relation19:25
hatch^ rick_h__  this is a bug?19:25
rick_h__hatch: because it's uncommitted now no19:27
rick_h__hatch: because it's not confirming an action19:27
hatcheven on a deployed relation though too19:27
rick_h__hatch: right, but when you remove it, you'll have to go commit19:28
hatchI know relations are 'supposed' to be idempotent, but I'm nto sure if we want to encourage the use of that :)19:28
rick_h__and see it in the summary/etc19:28
hatchohhh I get it19:28
rick_h__hatch: it's a bit like asking you "are you sure you want to possibly do X"19:28
hatchok when you delete the relation from the service inspector it pops up a dialogue19:28
hatchso I should remove that code now?19:28
hatcher.....under mv that is19:28
rick_h__hatch: ah, ok. Yea, welcome to clean that out if it's a small thing19:28
rick_h__hatch: or create a post-mv release card19:28
rick_h__but yea, the idea is that uncomitted state takes the place of 'are you sure'19:29
hatchwe will still need it if it's non mv unfortunately heh so I'll just wrap it with a mv flag check19:29
rick_h__hatch: right, or just leave it for now and add a cleanup card19:30
rick_h__hatch: as I'd like to see about this card landing to clear a release on monday?19:30
hatchyeah I'll timebox at 30min19:31
rick_h__k thx19:32
hatchjust writing tests now19:41
hatchshould have it up soonish19:41
hatchohh right the other thing in this bug is the unit name being a link https://bugs.launchpad.net/juju-gui/+bug/1350505 is this link supposed to open the unit details pane?19:46
_mup_Bug #1350505: Relation inspector does not have actions attached properly <juju-gui:New> <https://launchpad.net/bugs/1350505>19:46
hatchor should we remove the link19:46
hatchI'm leaning towards the former19:46
hatchrick_h__ ^19:52
hatchI could easily just remove the <a> for now as well if you wanted this to land sooner19:53
hatchMakyo thoughts on the unit link in the relations pane?19:54
MakyoNot sure.  I could see removing it as a temporary thing until we have word from design.19:55
hatchok sounds good,19:56
hatchdd19:56
hatchfixed19:56
hatch:P19:56
jrwrenManchester United v. Real Madrid here tomorrow. So I'm off to the party downtown. Have a great weekend.20:53
hatchjujugui looking for a review and qa on https://github.com/juju/juju-gui/pull/474 urgent bug required for release20:57
hatchjrwren enjoy, try to not fall over and cry20:57
hatch(little anti-soccer joke there)20:59
bachatch: new pycon web site up at https://us.pycon.org/2015/ -- shouldn't i be able to see that in french?20:59
hatchit is...can't you see the accent on Montreal21:00
hatchlol21:00
hatchbut yeah I'm pretty sure because it's in Quebec they have some rule about that21:00
hatchbac you should review my branch :)21:06
bachatch: done, but i can't do QA atm21:09
bachatch: gotta dash.  have a good weekend/week.21:09
hatchnp thanks21:10
hatchyou too, safe travels21:10

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