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

=== urulama_ is now known as urulama
rogpeppe1mornin' all07:12
urulamamorning07:12
huwshimimorning07:16
rogpeppe1urulama, huwshimi: hiya07:20
=== rogpeppe1 is now known as rogpeppe
=== rogpeppe1 is now known as rogpeppe
rogpeppefrankban: yo!08:57
frankbanmorning rogpeppe 08:58
rogpeppefrankban: you up for continuing forward with the store stuff?08:58
frankbanrogpeppe: sure, coffee and I am ready09:00
rogpeppefrankban: cool09:00
frankbanrogpeppe: I am in daily standup09:10
rogpeppefrankban: joining09:10
frankbanurulama: could you please take a look at https://github.com/juju/charmstore/pull/12 ?09:40
frankbanurulama: (and morning ;-)09:40
urulamafrankban: morning09:42
urulamafrankban: looks fine, only small detail ... you use CharmArchive sometimes instead of Archive (all the rest cases) ... any particular reason for this?09:47
urulamafrankban: (ie, branch_test.go, line 83)09:49
frankbanurulama: we (will) also have BundleArchives09:50
urulamafrankban: all clear09:50
=== nottrobin_ is now known as nottrobin
jrwrenmornin12:36
urulamamorning12:40
urulamajujugui: anyone else having problems with the login window after getting 1.20.0 core in the update? can't enter password for user-admin on any browser (firefox, chrome, safari)13:04
frankbanurulama: trying to reproduce13:05
urulamajujugui: whatever is typed is lost within a few sec (self erased)13:05
frankbanurulama: I am able to log in into the GUI in a local env13:10
urulamafrankban: ok, tnx. using manual here, switching to amazon now13:11
bachi frankban13:14
frankbanbac: morning, how are you doing?13:15
bacfrankban: good, thanks.  on friday, doing QA for quickstart i ran into bug 1316174 and suspended the release.  can't recall if i mentioned it or not.13:16
_mup_Bug #1316174: 'precise-updates/cloud-tools' is invalid for APT::Default-Release <juju-core:Triaged> <https://launchpad.net/bugs/1316174>13:16
bacfrankban: it isn't a QS issue but i didn't want to do a friday release with an issue13:16
frankbanbac: isn't it something also affecting current release?13:17
bacfrankban: yes it does13:17
frankbanbac: so, a new release would keep failing on precise but at least would fix trusty IIUC13:17
bacfrankban: yes, it would be an improvement13:18
frankbanbac: in this case I'd be +1 on releasing anyway.13:18
bacfrankban: qa on trusty was fine13:18
bacfrankban: ok, unfortunately i am not here today.13:19
frankbanbac: oh, I can do that then, so missing bits are 1) QA on saucy 2) move the packages to juju stable PPA and 3) push the release to PyPI, correct?13:19
bacfrankban: and the homebrew bits13:20
frankbanbac: ok, I see the hacking file includes brew documentation. I'll take care of the release, thanks a lot for the heads up while on holiday. 13:23
bacfrankban: np13:23
rogpeppefrankban: ready to continue whenever you are13:37
frankbanrogpeppe: joining13:39
urulamafrankban: seems like local, amazon & openstack env work properly, while manual has the issue with the login in juju-gui13:54
urulamafrankban: will test on some other machine, to see if i get the same error in manual env13:54
frankbanurulama: ok, let me know if you see the same13:56
hatchmorning all14:28
frankbanmorning hatch 14:41
hatchfrankban I've gone through about 4 more versions of the 'runWhenCalled' testing implementation heh14:41
hatchand still need to do one more :)14:41
frankbanhatch: after that, 3 more and I'd expect it to be just perfect14:42
hatchhaha - well I need it to finish these tests so those iterations better come quick :)14:44
hatchthe last iteration didn't work because it was hard to follow for many steps through the UI https://gist.github.com/hatched/087d9e30e3eb92a46657 see I added // #'s to illustrate that14:45
hatchthe current one does away with all that so you can write them synchronously 14:45
hatchexcept for the initial async call has to be called last....which I don't like14:46
hatchfrankban maybe you have a better idea https://gist.github.com/hatched/42e60957927b7caddd8b#file-test-js-L1414:47
hatchthat's the current functionality14:48
hatchI like how it's written synchronously but it's the initial 'trigger' that has to be put at the end which is a little funky - I was considering adding a `runner.step()` method which would parse the steps first then run a `runner.start()` but that's adding even more code to the test runner which I was really trying not to do14:49
hatchjujugui call in 514:55
hatchjujugui call in 114:59
hatchjujugui call now15:01
hatchkadams54 https://plus.google.com/hangouts/_/gwrfc6s6hbqazst3ovh3uaypeua?authuser=1&hl=en15:08
hatchhurrroowwww15:09
jcsackettjujugui: sorry i missed call time. have been knocked offline for last 30min and lost my phone.15:19
hatchjcsackett np15:19
kadams54hatch: sooooo…15:24
kadams54hatch: it looks like we check for that 'new' prefix in other parts of the code15:24
kadams54And use it to make decisions about whether the machine is committed yet or not.15:24
hatchok that's not going to work for the future15:24
kadams54What should we be doing?15:25
hatchwe should inspect the model to see if it's a real-boy15:25
hatchlater on we will add the ability to name machines15:25
hatchso we can't rely on a user input to know if something is new or not15:25
kadams54Well, it's not really user input, since it's a standard string we prefix to all machine IDs.15:26
kadams54(for uncommitted machines)15:26
kadams54The one advantage I see is that it means we don't have to do a DB lookup15:26
hatchright but that's not going to work15:26
hatchunless we have newthisismymachinename15:27
hatchor what if they name their machine 'newsuperbox'15:27
kadams54Name doesn't matter15:27
kadams54It's combining "new" + ID15:27
kadams54And I think ID is an auto-generated sequence?15:27
hatchcan you link me to where this is happening15:28
kadams54Just grep through machine-view-panel.js for 'new' (with single quotes included in the search) - it happens all over the place in there.15:29
kadams54Also: I'm not seeing a connection between the IDs of committed machines and the IDs assigned to ghosted machines, which would mean more overlap.15:30
kadams54The ghosted IDs are assigned via the _ghostCounter, which is just set to 0 when a MachineList is instantiated.15:31
hatchbut the name being displayed to the user is the id right?15:34
kadams54Not really15:36
kadams54It's just a temporary ID15:36
kadams54Which is created from 'new' + _ghostCounter15:36
kadams54And _ghostCounter has no connection to the actual IDs stored in the DB.15:37
kadams54So a machine could be new0 when created15:37
kadams54But 1 once actually deployed15:37
jcsacketthatch: i'm looking through your review, and i'm wondering, how would you feel about the various "createInspector" methods dealing with destroying the old one after they make a new one?15:37
jcsacketthatch: rather than the _inspector method tracking active and previous the whole way through?15:37
jcsackettat the point where we're, say, making createServiceInspector responsible for sorting out quite a bit about the state of the service inspector, it seems tidier to me.15:38
hatchkadams54 right, but what's being shown to the user? something is generating that15:38
hatchjcsackett hmm lemme take a look15:38
kadams54hatch: what's being shown to the user is exactly what I just said. 'new' + _ghostCounter15:39
hatchkadams54 so your card is simply deleting that 'new' ?15:39
kadams54Yes, and I'm saying it's not "simply" and we might want to re-think it.15:40
hatchyou think that we should leave the 'new' prefix?15:41
kadams541) we have logic based on the 'new' prefix and 2) we'll end up with a confusing UX because the user will see two machines labeled "0" and the only diff between them is that one is blue.15:41
kadams54hatch: yes.15:41
kadams54hatch: keep the new prefix, unless there's a strong case for removing it. In which case we'll need to get creative with solutions.15:42
hatch1) this is not going to work in the future, we can't rely on something saying 'new' if the user can enter their own names15:42
hatch2) I propose that we dont' show id's at all for undeployed machines if we can't show a reliable id15:43
hatchnew0 is just as confusing as 015:43
kadams54hatch: is naming machines on the road map?15:43
hatchyes, it's even in the bug report...15:43
kadams54new0 isn't great…15:43
kadams54But it's better than 015:43
kadams54It communicates something important about the machine's state15:43
kadams54Something that distinguishes new0 from 015:44
urulamafrankban: so, i've set up completely new set of machines for manual env and the "disappearing" password is no longer there. however, connecting to the juju environment fails now :(15:44
hatchkadams54 right, but new0 seems like it's a new version of 0, when in fact it's an entirely different machine15:44
kadams54hatch: I'll concede that point, but it's still better than having two machines labeled as "0"15:45
kadams54hatch: I don't like the way things currently work, but I don't think "simply" removing the "new" prefix is a step in the right direction.15:45
hatchjcsackett so instead of doing the previous inspector assignment in _inspector and then the previous.destroy in the _inspector you want to move that into the create methods?15:45
jcsacketthatch, i think so. can you chat for a moment?15:46
hatchkadams54 ok that's fine - so you need to send an email to design and peeps expressing your concerns and offering an alternative approach so that everyone can weigh in15:46
hatchjcsackett sure just one minute I need to relocate15:46
kadams541) We need to change the logic to look at a model attribute to determine uncommitted state and 2) we need to figure out how to differentiate (beyond blue color) ghosted machines from committed machines.15:46
jcsacketthatch: cool.15:46
hatchconstruction crews are making a ton of noise 15:46
kadams54hatch: will do.15:47
jcsackettalways fun, the construction.15:47
frankbanrbasak: quickstart 1.4.1 is on PyPI15:47
hatchjcsackett https://plus.google.com/hangouts/_/gs4t7bkjwkdpdylcfqa4a2nuwaa?authuser=1&hl=en15:50
=== urulama is now known as uru-afk
hatchjcsackett ok creating a new hangout16:14
hatchjcsackett https://plus.google.com/hangouts/_/gvbizv4vjesvksrba5nljzslq4a?authuser=1&hl=en16:15
hatchkadams54 thanks for the email16:48
kadams54yup16:48
hatchkadams54 I usually add luca directly to these emails as I'm not sure  he's on peeps, maybe keep that in mind and ping him next time you see to make sure he got it16:50
kadams54Yeah, I CC'd him on this.16:50
kadams54Rick had mentioned the same.16:50
hatchoh I didn't see it in the list16:52
hatchmaybe you bcc'd?16:52
kadams54From: Kyle Adams <kyle.adams@canonical.com>16:53
kadams54To: "juju-gui-peeps@lists.launchpad.net" <juju-gui-peeps@lists.launchpad.net>16:53
kadams54Cc: Luca Paulina <luca.paulina@canonical.com>16:53
kadams54I suspect the list stripped off the CC.16:53
hatchinteresting I didn't know it did that16:54
hatchin fact I didn't think that it did heh16:54
kadams54Taking a lunch break…17:33
* rogpeppe is done for the day17:46
rogpeppeg'night all17:46
hatchcya rogpeppe 18:01
hatchjujugui anyone around to take a look at a complicated test using my new 'resume' method? https://gist.github.com/hatched/a115fb081279c8856b9d18:01
hatchthis technique now allows you to test async UI interactions by writing synchronous code18:01
hatchhere is the changes to the utils methods and it in use https://gist.github.com/hatched/087d9e30e3eb92a4665718:08
jcsacketthatch: FYI, won't have branch up before my usual EoD. Doc appt has been 2.5 hours and ain't over yet. 19:54
hatchyikes, ok np19:54
hatchlots of waiting room?19:55
hatchjujugui looking for a review and qa https://github.com/juju/juju-gui/pull/425 plz and thanks20:00
hatchI'm blocked on my next task until that branch lands20:01
hatchwell I can just continue from it, np20:02
hatchjujugui does anyone know how the user will 'scale-down' with the new scale-up UI?20:50
rick_h__bac: around? 21:19
hatchhmm, does anyone know why a simulate() call wouldn't work in IE in a callback?21:25
hatchrick_h__ no he is off today21:25
hatchended up working Friday instead21:25
rick_h__hatch: ok cool21:25
hatchand wb to the real world21:25
hatch:)21:25
rick_h__hah, no kidding21:25
rick_h__wheeee21:25
rick_h__start driving home and all the emails start to arrive21:25
hatchhaha, ding ding ding ding.......21:26
rick_h__there's still places out there with no cell connectino21:26
hatchyeah our cabin used to be one....unfortunately (fortunately?) it now has reception21:26
hatchwell I'm totally baffled by this test failure22:08
hatchof course it has to be in IE10 too hah22:08
hatchhmm it happens in all versions of IE22:27
hatcheven 1122:27
hatchkadams54 wb22:27
hatchwell I'm at a total loss here maybe a night off will give me some fresh perspective 22:32
huwshimiMorning23:07
rick_h__morning huwshimi 23:07
rick_h__how goes?23:07
huwshimirick_h__: Hey, good thanks. Have a nice break?23:07
rick_h__huwshimi: yea, have 996 pictures to go through :)23:12
rick_h__good times, a little crazy having no cell reception for days at a time23:12
rick_h__but was good and exhausting times in the woods23:12
huwshimirick_h__: Great! It's cool to hear how you actually get away during your breaks :)23:13
huwshimiI guess that usually doesn't stop you from working though :)23:14

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