[07:55] <Saviq> mzanetti, ping
[07:56] <mzanetti> morning Saviq
[07:56] <Saviq> mzanetti, hey, any idea about https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-saucy/850/console
[07:56] <Saviq> mzanetti, ERROR:pbuilderjenkins:H05set_package_version not found in hooks
[07:57] <mzanetti> Saviq: not seen yet... let me check existing hooks
[07:57] <Saviq> mzanetti, btw dh_install: usr/share/unity8/plugins/mocks/Unity/Launcher/libMockLauncherPlugin.so exists in debian/tmp but is not installed to anywhere
[07:57] <Saviq> dh_install: usr/share/unity8/plugins/mocks/Unity/Launcher/qmldir exists in debian/tmp but is not installed to anywhere
[07:57] <mzanetti> ok. I'll fix that
[07:58] <Saviq> mzanetti, I think it might've changed with fginther adding our local repo yesterday
[07:58] <Saviq> mzanetti, I mean the hook
[07:58] <mzanetti> Saviq: yeah... seems so
[08:03] <mzanetti> Saviq: oh crap... thats a mess
[08:03] <Saviq> mzanetti, :/
[08:04] <mzanetti> Saviq: the jobs pull hooks from 3 different sources
[08:04] <Saviq> eek
[08:04]  * mzanetti is not going to clean this up now...
[08:05] <mzanetti> I'll try to just remove the set_version hook from the mediumtests job
[08:06] <mzanetti> not possible :/
[08:09] <Saviq> mzanetti, who do we have in our timezone that could help us fix?
[08:10] <mzanetti> Saviq: yeah... thats actually a problem... there is no QE in europe timezone any more
[08:10] <Saviq> right :/
[08:10] <mzanetti> well, vrruiz is, but he's mostly busy with webapp stuff
[08:10] <Saviq> yeah, we're hiring for that, probably, then
[08:11] <mzanetti> Saviq: anyways, that missing hook comes from a branch owned by fginther
[08:11] <mzanetti> Saviq: and that branch is pulled in the builder jobs but not in the others
[08:11] <mzanetti> Saviq: I'm trying to pull the hook from there and add it to where it belongs. the real hooks package
[08:11] <Saviq> mzanetti, thanks
[08:11] <Saviq> mzanetti, why can't you remove it btw?
[08:12] <mzanetti> because they are inherited from upstream jobs
[08:12] <Saviq> mzanetti, which are configured autmagically
[08:12] <mzanetti> and if I remove it upstream it won't bump the version number any more
[08:12] <mzanetti> which would cause the local repository to break I'd assume
[08:13] <Saviq> mzanetti, yeah, it's probably for that (it needs to mangle the changelog to actually do a release)
[08:13] <mzanetti> yep
[08:13] <Saviq> mzanetti, btw, did qmluitests get the local repo added, too?
[08:13]  * mzanetti checks, but I would assume no
[08:15] <mzanetti> Saviq: qmltests does not use the inherited hook list
[08:15] <mzanetti> Saviq: because that's a specific job for unity8 so it has the required unity8 hooks hardcoded
[08:16] <Saviq> mzanetti, yup, we should add the one that adds the local repo, right?
[08:16] <mzanetti> Saviq: guess so, yes... let me first fix the mediumtests one.
[08:17] <mzanetti> btw. why is our code coverage dropping like crazy?
[08:17] <mzanetti> Saviq: ^
[08:18] <Saviq> mzanetti, are you looking at -ci or at -autolanding?
[08:18] <mzanetti> both... right now autolanding
[08:18] <Saviq> mzanetti, anyways, indicators-client isn't tested well yet
[08:19] <mzanetti> oh right... that was my problem child already when I was in the apps team
[08:19] <Saviq> mzanetti, yeah, we're taking it over and we'll be improving that
[08:19] <Saviq> mzanetti, at least the QML part
[08:20] <Cimi> mzanetti, how about this? http://paste.ubuntu.com/5857753/
[08:22] <Saviq> mzanetti, also, somehow we started gathering coverage for tests again, need to fix that to get some real-ish numbers
[08:24] <mzanetti> Cimi: what's this?
[08:24] <Cimi> mzanetti, instead of clearing the model
[08:24] <Cimi> mzanetti, I push/append
[08:24] <mzanetti> Cimi: ok. give me a minute for my current task, then I'll re-review
[08:25] <Cimi> mzanetti, it's a WIP
[08:25] <Cimi> mzanetti, like, this works but I believe there might be flaws
[08:25] <Cimi> mzanetti, like if you clear also the buffer and remain with one or two items, will it scroll?
[08:26] <Cimi> maybe since onCurrentIndex should populate the sides...
[08:26] <Cimi> might have to test
[08:26] <mzanetti> Cimi: ah ok... yeah, I can give it a closer look in a few. Not sure either how the thing behaves in that situations
[08:26] <Cimi> mzanetti, it's the corner cases indeed
[08:26] <Cimi> mzanetti, when something changes currentDate or maximum/minimum
[08:27] <mzanetti> Saviq: https://code.launchpad.net/~mzanetti/pbuilderjenkins/add-missing-hooks/+merge/173668
[08:28] <mzanetti> Saviq: I'm not entirely sure if fginther will be happy about this... but the current state doesn't work either... So I'd say we go for it and if fginther doesn't like it, I'll help him finding a proper solution
[08:28] <Saviq> mzanetti, yeah, we need to unblock
[08:28] <mzanetti> (I think this is the proper solution though)
[08:29] <Saviq> mzanetti, approved
[08:29] <mzanetti> Saviq: ok... once this landed, I need to update the pbuilderjenkins package in the mediumtests vm's. Then it should work again
[08:30] <Saviq> mzanetti, k, thanks
[08:45] <mzanetti> Saviq: as usual, I forgot to release. Could you approve this one too: https://code.launchpad.net/~mzanetti/pbuilderjenkins/relase-new-hooks/+merge/173670
[08:46] <Saviq> mzanetti, UNRELEASED ok
[08:46] <Saviq> ?
[08:46] <mzanetti> huh? didn't I release
[08:46] <mzanetti> one sec
[08:47] <mzanetti> Saviq: now
[08:47] <Saviq> mzanetti, saucy ok?
[08:47] <Saviq> mzanetti, the previous ones are raring
[08:47] <mzanetti> Saviq: yeah... there hasn't been a release in a while...
[08:47] <Saviq> k
[08:51] <mzanetti> Cimi: this seems broken:
[08:51] <mzanetti> +        while (i < calendarModel.count && calendarModel.get(i).monthStart < minimumDate) {
[08:51] <mzanetti> +            calendarModel.remove(0)
[08:51] <mzanetti> +            i++
[08:51] <mzanetti> +        }
[08:51] <mzanetti> Cimi: you do a get(i++) and a remove(0).
[08:51] <mzanetti> Cimi: seems like you're skipping every second one
[08:52] <Cimi> mzanetti, indeed
[08:52] <Cimi> mmm
[09:07] <mzanetti> tsdgeos: I can reproduce it now
[09:07] <tsdgeos> mzanetti: shoot
[09:07] <mzanetti> tsdgeos: go to the music lens
[09:07] <mzanetti> tsdgeos: drag it a little bit up, so that most of the header is hidden
[09:08] <mzanetti> tsdgeos: but not all of it. the thick sepearator should still be visible
[09:08] <tsdgeos> mzanetti: on the phone, right?
[09:08] <mzanetti> tsdgeos: yes
[09:08] <mzanetti> tsdgeos: then drag it to the right (moving content to the right, which would get you to the lens on the left, if there would be one)
[09:08] <mzanetti> tsdgeos: the header will come back
[09:08] <mzanetti> tsdgeos: release, and drag again
[09:09] <mzanetti> tsdgeos: the header will come down a bit more
[09:09] <mzanetti> tsdgeos: and with every drag it goes further down. once it reaches the bottom of the screen the whole lens is messed up and ever interaction breaks it more
[09:09] <tsdgeos> blame qreal :D
[09:09] <mzanetti> haha
[09:09]  * mzanetti blames qreal
[09:10] <tsdgeos> i'll have a look
[09:10] <tsdgeos> i had this before
[09:10] <tsdgeos> thought it was fixed
[09:10] <mzanetti> tsdgeos: its an image from yesterday morning
[09:12] <mzanetti> *boom*
[09:14] <Saviq> yowza
[09:14] <Saviq> tsdgeos, yeah, my header just went far down, it's just GONE! ;)
[09:15] <Saviq> tsdgeos, and the content went up, it's GONE, too :D
[09:16] <mzanetti> Saviq: yep. thats the one :D
[09:16] <mzanetti> Saviq: reproducable with the left/rightmost lens
[09:17] <Saviq> mzanetti, made it with Home, too
[09:17] <mzanetti> Saviq: I've seen it once there. but way harder to reproduce there
[09:17] <mzanetti> Saviq: also, slide the header a little out the screen and tap on search. sometimes it'll come in without moving/clipping the listview
[09:18] <mzanetti> it == the search field
[09:18] <tsdgeos> yeah can repro the thing
[09:18] <tsdgeos> :/
[09:18] <tsdgeos> will work on it
[09:19] <mzanetti> tsdgeos: well, if you can reproduce it, isn't that half of the win?
[09:19] <tsdgeos> does pphablet-flash give me a flipped image already?
[09:19] <Saviq> mzanetti, yeah, it's the same code - showHeader()
[09:19] <tsdgeos> mzanetti: :D
[09:19] <Saviq> tsdgeos, yes
[09:19] <mzanetti> tsdgeos: imagine you couldn't reproduce it and it happens randomly... that would suck
[09:19] <tsdgeos> Saviq: do we need any adjustment on run_on_Device or just works?
[09:19] <mhr3_> Saviq, the osk doesn't seem to work with latest image, known?
[09:19] <tsdgeos> mzanetti: well one could say it happens randomly since on the PC it works :D
[09:20] <mzanetti> :D
[09:20] <mhr3_> Saviq, well, in the scope views
[09:20] <Saviq> mhr3_, yeah, OSK is broken
[09:21] <mzanetti> tsdgeos: run_on_device is already adusted for flipped images
[09:21] <mhr3_> Saviq, any workaround?
[09:21] <Saviq> mhr3_, 'fraid not
[09:22] <tsdgeos> mzanetti: greatz
[09:22]  * tsdgeos goes to pay some taxes while the newer image is being downloaded
[09:22] <Saviq> mhr3_, bug #1199150
[09:26] <mhr3_> thx
[09:32] <nic-doffay> Saviq, for the container of the expandable, should the expanding call set a property on the container which is a child? This is specifically for the animations and all.
[09:32] <nic-doffay> expanding signal sorry
[09:32] <nic-doffay> Am I making sense?
[09:33] <Saviq> nic-doffay, you lost me at "container which is a child" :D
[09:33] <nic-doffay> Let me pastebin a quick example.
[09:34] <nic-doffay> Saviq, here's an example minus everything else of what I meant: http://pastebin.ubuntu.com/5857906/
[09:34] <Saviq> nic-doffay, sure
[09:34] <Saviq> nic-doffay, only you don't need (Item expandable)
[09:35] <Saviq> nic-doffay, you can use "sender"
[09:35] <nic-doffay> Saviq, cool.
[09:35] <Saviq> I _think_?
[09:35] <nic-doffay> I also obviously have to set the Container in the expandable.
[09:35] <Cimi> mzanetti, with get(0) should work http://paste.ubuntu.com/5857909/
[09:36] <Saviq> nic-doffay, yeah, you need to pass it, I thought sender is available, but apparently it isn't
[09:36] <nic-doffay> Saviq, so basically the OptionSelector now works whether there's a scrollable container as a parent or not.
[09:36] <nic-doffay> Since this Container is another optional component.
[09:37] <Saviq> nic-doffay, yeah, and ideally it still should work without the Container
[09:37] <nic-doffay> Saviq, that's what it does atm.
[09:38] <nic-doffay> Saviq, however what class should the expandable be passed into that signal as?
[09:38] <nic-doffay> Item is a bit vague.
[09:38] <Saviq> nic-doffay, ListItem.Expandable, probably, when you introduce it :)
[09:39] <Saviq> nic-doffay, don't optimize prematurely
[09:39] <nic-doffay> Saviq, what base feature would ListItem.Expandable have that the OptionSelector doesn't though?
[09:39] <nic-doffay> I'm assuming you mean for the ListItem.Expandable to be a base class for all of these?
[09:39] <Saviq> nic-doffay, it can be inherited by other components
[09:40] <Saviq> nic-doffay, hmm
[09:40] <nic-doffay> Saviq, just the expanding logic?
[09:41] <Saviq> nic-doffay, it should have `real collapsedHeight`, `real expandedHeight`, `bool expanded` at least
[09:42] <Saviq> nic-doffay, just think which would be common between the OptionSelector and the expanding Message items you did before
[09:43] <Saviq> nic-doffay, it's not like I can tell you from the top of my head what would that be :)
[09:49] <Saviq> paulliu, ping
[09:54] <mzanetti> Cimi: haven't tested it, but looks better, yes
[10:07] <nic-doffay> Saviq, what's the best way to get more output from a qmlscene?
[10:07] <nic-doffay> Something (nothing) unexplained is happening.
[10:07] <Saviq> nic-doffay, onPropertyChanged: console.log("something") usually
[10:07] <Saviq> nic-doffay, you can also run the debugger in QtCreator
[10:09] <nic-doffay> Saviq, I mean the qmlscene isn't even coming up for weird reasons.
[10:09] <nic-doffay> Need to find out why.
[10:09] <Saviq> nic-doffay, does your top-level object have dimensions?
[10:09] <nic-doffay> Saviq, yeah.
[10:10] <nic-doffay> Saviq, basically what I did was change that Item in the pastebin  I sent you to an OptionSelector, now nothing runs.
[10:10] <nic-doffay> Obviously an item won't have an expanded property.
[10:11] <Saviq> nic-doffay, sorry, quite busy now, we've failed miserably at a review yesterday
[10:11] <nic-doffay> Saviq, how so?
[10:11] <Saviq> nic-doffay, not you, /me and mzanetti
[10:12] <Saviq> but mostly me
[10:12] <nic-doffay> :(
[10:12] <mzanetti> huh?
[10:12] <mzanetti> the launcher-backend ones?
[10:18] <Saviq> mzanetti, no, the dee filtermodel
[10:18] <Saviq> mzanetti, it broke _everything_ in the dash
[10:19] <Saviq> on the device, that is
[10:19] <mzanetti> Saviq: hmm... weird. I ran it on the device tho... seemed to work
[10:25] <Saviq> mzanetti, it "works", but there's no data in Home other than apps, and no Installed in Apps
[10:25] <Saviq> mzanetti, not to mention icons and titles and such are broken everywhere
[10:26] <nic-doffay> mzanetti, have a moment to check something out?
[10:26] <mzanetti> nic-doffay: hit me
[10:27] <nic-doffay> Weird problem where I'm passing something to a signal but as soon as I change the class from Item to the class nothing works.
[10:28] <nic-doffay> mzanetti, lp:~nicolas-doffay/+junk/option-selector
[10:29] <nic-doffay> mzanetti, if you take a look at ScrollableExpansionContainer.qml in modules/Ubuntu/Components/ListItems
[10:29] <nic-doffay> You'll see an OptionSelector is passed from a signal.
[10:30] <nic-doffay> When this is an Item everything works properly.
[10:30] <nic-doffay> However obviously the class needs to be passed in to properly access the variable.
[10:30] <nic-doffay> Running test.qml in modules/Ubuntu/Components/ListItems you'll see what I mean.
[10:30] <nic-doffay> No output, nothing.
[10:33] <mzanetti> nic-doffay: there is no ScrollableExpansionContainer
[10:34] <nic-doffay> mzanetti, whoops one sec.
[10:38] <nic-doffay> mzanetti, pushed again.
[10:40] <paulliu> Saviq: hi
[10:40] <Saviq> paulliu, hey, thanks for spotting the video breakage... there's actually more of that elsewhere... am fixing now
[10:40] <Saviq> paulliu, it was an epic review fail on my part
[10:42] <paulliu> Saviq: ok.. I just fix the video lens to test my branch. :)
[10:42] <mzanetti> nic-doffay: this looks really scary
[10:43] <mzanetti> nic-doffay: what do you want to achieve with this?
[10:43] <mzanetti> nic-doffay: and why is this a signal?
[10:43] <mzanetti> to me this doesn't make any sense at all
[10:49] <nic-doffay> mzanetti, this container will handle scrolling for expandable SDK components.
[10:49] <nic-doffay> The signal is sent from the expandable component.
[10:49] <Saviq> paulliu, can you please include this diff in your MP http://pastebin.ubuntu.com/5858043/
[10:49] <mzanetti> nic-doffay: yeah... signals are supposed to be used when a component wants to emit something to the outside. not getting something from the outside
[10:50] <mzanetti> nic-doffay: also, why don't you just use a flickable then where you embed the other component that needs to be scrolled?
[10:51] <mzanetti> nic-doffay: do you have a spec how things should look like in the end? I'm having a hard time following what you want to do with this
[10:54] <paulliu> Saviq: ok
[10:58] <nic-doffay> mzanetti, there aren't any specs I'm aware of.
[10:58] <nic-doffay> mzanetti, let me forward you something though...
[10:58] <nic-doffay> mzanetti, you have mail.
[10:59] <tsdgeos> whattt
[10:59] <tsdgeos> now i can repro the header problem on the pc too
[10:59] <tsdgeos> :S
[11:04] <tsdgeos> btw do you guys get the images of "Music" in either pc or desktop?
[11:04] <tsdgeos> i'm just getting empty ubuntu shapes
[11:04] <tsdgeos> Saviq: mzanetti: Cimi: greyback: MacSlow: dednick: all :D↑↑↑
[11:04] <Saviq> tsdgeos, yes, we broke it yesterday
[11:04] <Saviq> tsdgeos, fixing now
[11:04] <MacSlow> tsdgeos, ?
[11:04] <tsdgeos> ah
[11:04] <tsdgeos> ok
[11:04] <MacSlow> tsdgeos, not seen that issue yet
[11:05] <Saviq> mzanetti, Cimi, greyback, MacSlow, dednick, all: unping
[11:05] <MacSlow> Saviq, :)
[11:05] <mzanetti> :D
[11:05] <MacSlow> "unping"
[11:05]  * MacSlow notes that term in his memory
[11:05] <greyback> E_POP_EMPTY_STACK
[11:09] <mzanetti> nic-doffay: still don't get it... what is the use case for this? if I have an expanding component, why wouldn't it be expanded to what it needs to be?
[11:09] <nic-doffay> mzanetti, the idea is that this container can be used for any expanding component instead of coding it separately for each.
[11:10] <mzanetti> nic-doffay: ah. so the expanding component itself would always be expanded, but just clipped by the container?
[11:11] <nic-doffay> mzanetti, no.
[11:12] <nic-doffay> mzanetti, the expanding item would call the container which would in turn set the expansion on the expanding item and handle the animation and movement
[11:12] <nic-doffay> does that make any sense?
[11:13] <mzanetti> nic-doffay: not for me... but according to this mail it does make sense for Saviq. So I must be missing something here.
[11:13] <Saviq> mzanetti, lol
[11:14] <mzanetti> :)
[11:14] <mzanetti> what should I say
[11:14] <mzanetti> thats how it is :D
[11:14] <nic-doffay> mzanetti, haha
[11:14] <Saviq> nic-doffay, the height animation could happen in the Expandable base component itself
[11:14] <Saviq> mzanetti, do you know what the whole deal is about?
[11:15] <mzanetti> Saviq: not really, no
[11:15] <Saviq> mzanetti, an item in a list
[11:15] <Saviq> mzanetti, the item is expandable, i.e. it can change its height
[11:15] <mzanetti> yeah. so far I'm good
[11:15] <Saviq> mzanetti, but when it expands, it should be limited to the list's height
[11:15] <Saviq> mzanetti, and it should be scrolled into view
[11:15] <mzanetti> what's the "list" ?
[11:16] <Saviq> mzanetti, anything, a ListView, say
[11:16] <mzanetti> oh... I see...
[11:16] <Saviq> mzanetti, and an item in that ListView needs to be able to expand
[11:16] <mzanetti> the scrolling thing is interesting.
[11:16] <Saviq> mzanetti, and when it does, it needs to be constrained to the ListView's height
[11:16] <Saviq> mzanetti, and then scroll it into view
[11:16] <Saviq> mzanetti, yup
[11:16] <mzanetti> right...
[11:17] <Saviq> mzanetti, when the item is smaller than the ListView
[11:17] <Saviq> mzanetti, it should be minimal travel
[11:17] <Saviq> to show that whole item
[11:17] <mzanetti> ok... I start to understand...
[11:17] <mzanetti> thanks Saviq
[11:17] <Saviq> mzanetti, so the ListView needs to know the item's expanded and collapsed heights
[11:17] <Saviq> mzanetti, and change them accordingly
[11:18] <Saviq> mzanetti, I might've overcomplicated things in the email, too :)
[11:19] <mzanetti> why would the listview need to know both sizes?
[11:19] <mzanetti> ah no... the listview is the one to scroll
[11:19] <mzanetti> ok...
[11:21] <mzanetti> nic-doffay: ok... so the naming ScrollableExpansionContainer is the first misleading thing. I thought the content in there needs to scroll, not the listview around it
[11:22] <nic-doffay> mzanetti, you're right the content within does.
[11:22] <nic-doffay> mzanetti, maybe ScrollableContainer is more reasonable?
[11:22] <Saviq> mzanetti, how are we re: jenkins?
[11:22]  * mzanetti checks (should work by now)
[11:23] <mzanetti> Saviq: I ran a mediumtests job manually and it worked
[11:23] <Saviq> mzanetti, k thanks
[11:24] <mzanetti> Saviq: but wouldn't we need to have our own ListView implementation to support this kind of stuff?
[11:26] <Saviq> mzanetti, no, why?
[11:27] <Saviq> mzanetti, we just need to have a channel of communication between the Flickable / Scrollable and the Expandables
[11:27] <mzanetti> but where is the code that scrolls the flickable?
[11:28] <mzanetti> Saviq: the expandable itself?
[11:28] <Saviq> mzanetti, no, in the Flickable
[11:29] <Saviq> mzanetti, it knows which Expandable it needs to scroll to
[11:29] <Saviq> mzanetti, because the Expandable will signal Scrollable.RequestExpansion(self) (pseudo code)
[11:30] <nic-doffay> mzanetti, that's what it currently does.
[11:30] <mzanetti> nic-doffay: ah... so we're not talking about a flickable that uses those components... but another flickable inside the list
[11:31] <Saviq> mzanetti, then, the Scrollable will map to its own coordinates and scroll accordingly, animating the height in parallel (that can happen either in Scrollable directly or the Expandable could have  a Behavior, but that could be wasteful when you only ever animate one Expandable at a time)
[11:31] <Saviq> mzanetti, hum?
[11:32] <mzanetti> where would you place such a component? do you have an example?
[11:32] <mzanetti> I really dont see the usefulness of such a thing (except maybe the reviews in scopes)
[11:32] <mzanetti> previews
[11:32] <nic-doffay> mzanetti, this is the thing.
[11:33] <nic-doffay> Everyone is debating this.
[11:33] <nic-doffay> Design doesn't even have a proper mock up yet.
[11:35] <mzanetti> nic-doffay: anyways... ignoring that... let me write some pseudocode how I would try to approach the problem
[11:36] <mzanetti> (besides asking design for clear guidance)
[11:36] <nic-doffay> mzanetti, done that bit already.
[11:36] <nic-doffay> Any idea about that original issue out of interest?
[11:44] <Saviq> mzanetti, mhr3_, https://code.launchpad.net/~saviq/unity8/fix-mock-scopes/+merge/173698
[11:44] <mzanetti> nic-doffay: http://paste.ubuntu.com/5858161/
[11:44] <mzanetti> nic-doffay: hope that makes somehow sense
[11:44] <mzanetti> Saviq: on it
[11:44] <Saviq> mzanetti, re ↑↑↑ http://design.ubuntu.com/apps/building-blocks/option-selector
[11:45] <Saviq> http://design.ubuntu.com/apps/building-blocks/expansion
[11:45] <mzanetti> Saviq: for that I don't see why we would need such a construct
[11:45] <mzanetti> Saviq: instead of just placing a normal expanding component into a ListView
[11:46] <mzanetti> Saviq: and perhaps making the ListView "interactive: contentHeight > height"
[11:46] <Saviq> mzanetti, it's not always a ListView, mind you, it can be as simple as a Column
[11:46] <Saviq> mzanetti, a Column in a Flickable, that is
[11:46] <Saviq> mzanetti, it's actually going to be the more common use, I'd say
[11:46] <mzanetti> Saviq: s/ListView/Flickable/
[11:47] <mhr3_> Saviq, why is the Qt.binding necessary?
[11:47] <Saviq> mhr3_, otherwise it only sets the value once
[11:47] <Saviq> mhr3_, whereas with Qt.binding it will update when changed
[11:48] <Saviq> mhr3_, so when you send dataChanged(i, i, RoleResults), it will update automagically
[11:48] <mhr3_> clever
[11:48] <Saviq> mhr3_, we should be able to test by killing the backends, right?
[11:48] <Saviq> mhr3_, as the Scope object itself won't change, nor the Categories will
[11:49] <nic-doffay> mzanetti, yeah that makes sense. Cleaner imo
[11:49] <mhr3_> ok, looks fine to me, but perhaps it'd be better to add also the s/column_/.../ changes?
[11:49] <mhr3_> Saviq, yep
[11:49] <Saviq> mhr3_, prereq
[11:51] <mhr3_> Saviq, i'd suggest merging it in, one won't work without the other, will it?
[11:52] <Saviq> mhr3_, works fine, it fixes two different issues
[11:52] <Saviq> mhr3_, with the prerequisite apps and videos will get fixed
[11:52] <Saviq> mhr3_, with my MP only the "peeking" into other scopes is being fixed
[11:54] <mhr3_> ah, ok, i thought that the raw model is still used by some of the renderers
[11:55] <Saviq> mhr3_, we need to re-search after the scope is reconnected after it's killed, right?
[11:55] <mhr3_> Saviq, yea
[11:55] <Saviq> mhr3_, 'cause now my model is updated, but the results are not
[11:55] <Saviq> mhr3_, k, separate MP then
[12:06] <Saviq> mhr3_, "m_unityScope->Search(m_searchQuery.toStdString());" is missing the callback, right?
[12:08] <mhr3_> Saviq, i'm just looking at that, and that should make sure that a re-search happens
[12:08] <Saviq> mhr3_, yeah, but there's no callback?
[12:08] <mhr3_> not sure why it doesn't
[12:08] <mhr3_> Saviq, right, but no biggie
[12:09] <Saviq> mhr3_, should work anyway?
[12:09] <mhr3_> yep
[12:09] <mhr3_> there'll be one missed searchFinished signal, don't think shell uses it anyway yet
[12:09] <Saviq> right
[12:10] <mzanetti> Saviq: oh noes! the hooks are there now, but one of them fails to execute
[12:10] <Saviq> mzanetti, ;(
[12:10] <mzanetti> Saviq: I fear we need fginther for this
[12:10] <mzanetti> only he know what this stuff is supposed to do
[12:11] <Saviq> it's a fail day if I know one
[12:14] <Saviq> mzanetti, nic-doffay now that I think of it again... I'm not sure the "constrain height to Scrollable's height" I described should actually happen
[12:15] <Saviq> nic-doffay, can you please confirm with ckpringle what should happen with "overflow"
[12:15] <Saviq> nic-doffay, because if we enable scrolling *inside* the Expandable in case of overflow, it kind of conflicts with the fact that you should be able to scroll to the other items
[12:15] <Saviq> nic-doffay, and the "expand in place" pattern
[12:18] <mzanetti> Saviq: I might have found the issue on jenkins... next test running...
[12:18] <Saviq> mzanetti, thanks
[12:19] <nic-doffay> Saviq, I'm busy waiting on confirmation about the actual expandable item too.
[12:19] <Saviq> nic-doffay, get busy prodding, then! :D
[12:19] <nic-doffay> Saviq, that's what I've been doing.
[12:19] <Saviq> nic-doffay, k :)
[12:22] <mzanetti> Saviq: yeah! thats exactly what I meant
[12:23] <Saviq> mzanetti, you mean flicking within another Flickable?
[12:23] <mzanetti> I mean... there might be use cases for such a thing. as I said, the DashPreview would be one.
[12:23] <mzanetti> but really not for such components as this is intended for
[12:24] <mzanetti> only if the content will always expand to fullscreen
[12:31] <sil2100> mhr3_: ping!
[12:31] <mhr3_> sil2100, pong
[12:31] <sil2100> mhr3_: who's the guy I should pester related to Unity dash Previews?
[12:31] <sil2100> mhr3_: you guys or dednick? (or someone else even?)
[12:32] <mhr3_> sil2100, what is the pestering about?
[12:32] <sil2100> mhr3_: failing AP tests of course!
[12:32] <sil2100> What else should I pester about? :)
[12:34] <mhr3_> sil2100, the same thing as on friday?
[12:34] <mhr3_> it wasn't really failing preview but failing dbus
[12:34] <mhr3_> probably cause of udev
[12:35] <sil2100> Not sure if the same, since I was out on Friday, but there's a lot of preview tests failing
[12:36] <sil2100> I see most failures look hm, sane: MismatchError: After 10.0 seconds test on DashView.preview_displaying failed: True != dbus.Boolean(False, variant_level=1)
[13:04] <dandrader> mzanetti, do you know what this error means? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-saucy/872/console
[13:04] <dandrader> random jenkins failure or do we have to do something?
[13:04] <mzanetti> dandrader: yes. I'm working on it. I just had a successful build again
[13:04] <mzanetti> dandrader: with a bit of luck you should be able to autoland again in a few minutes
[13:19] <kgunn> Saviq: hey, nic-doffay and i were just chatting....wondering if we might want to pick
[13:19] <kgunn> one of the scopes to actually tie up to the
[13:19] <kgunn> option expander as an example to try to drive some feedback
[13:20] <kgunn> i thought you might have one in mind ?
[13:20] <Saviq> kgunn, there's no backends hooked up yet
[13:20] <Saviq> kgunn, nic-doffay so just work with any of them
[13:20] <Saviq> off of dummy data
[13:21] <Saviq> mzanetti, ↑ see who joined? ;
[13:21] <Saviq> ;)
[13:21] <mzanetti> fginther: \o/
[13:21] <mzanetti> Saviq: but I think I just solved it :D
[13:21] <kgunn> nic-doffay: can you just go for it for say "music"
[13:21] <Saviq> mzanetti, fginther probably saw that you did :)
[13:21] <Saviq> fginther, that's why he joined ;)
[13:22] <fginther> uh oh
[13:22] <fginther> mzanetti, Saviq, I'm scared to ask what's going on :-)
[13:22] <Saviq> fginther, see all the red https://jenkins.qa.ubuntu.com/job/unity8-autolanding/ https://jenkins.qa.ubuntu.com/job/unity8-ci/ ? ;P
[13:23] <mzanetti> fginther: hehe
[13:23] <mzanetti> fginther: short summary:
[13:23] <mzanetti> the enabling of the local ppa broke mediumtests jobs
[13:23] <mzanetti> fginther: what I did:
[13:23] <fginther> ohhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
[13:24] <mzanetti> I merged the 2 hooks needed for the local ppa into pbuilderjenkins so we don't have to pull them from your bzr branch
[13:24] <mzanetti> fginther: then I modified the mediumtests jobs to receive the additional parameters required by those hooks
[13:25] <mzanetti> fginther: seems to work again now
[13:25] <fginther> mzanetti, oh, that sounds good
[13:25] <nic-doffay> kgunn, is there a design doc for easy reference?
[13:25] <mzanetti> fginther: still to do: get rid of your bzr branch and switch existing builders to use hooks from pbuilderjenkins
[13:25] <mzanetti> fginther: I hope I did not mess up something else :/
[13:25] <mzanetti> but it looks good now
[13:25] <fginther> mzanetti, I should have thought about that yesterday
[13:26] <fginther> mzanetti, very cool
[13:27] <mzanetti> Saviq: fginther: Victory! https://code.launchpad.net/~mzanetti/unity8/remove-unused-file/+merge/173568
[13:27] <mzanetti> merged ^^
[13:27] <fginther> mzanetti, nice. thanks for fixing
[13:27] <mzanetti> dandrader: you should be able to merge your stuff now
[13:27] <Saviq> nic-doffay, http://design.ubuntu.com/apps/building-blocks/option-selector those images show exactly that
[13:27] <nic-doffay> Saviq, cool.
[13:27] <nic-doffay> ta
[13:29] <kgunn> nic-doffay: yep....was going to paste the same
[13:30] <Saviq> dednick, paulliu standup
[13:31] <dandrader> mzanetti, ok, trying out
[13:33] <mzanetti> fginther: I did some more research regarding jenkins slowness and updated our doc
[13:33] <fginther> mzanetti, thanks, I'll take a look when I get a moment to breathe
[13:33] <paulliu> Saviq: ok
[13:33] <mzanetti> fginther: not in a hurry with this... just wanted to let you know
[13:36] <Saviq> fginther, btw, are any of the ps-saucy-server- machines unhooked?
[13:37]  * Saviq doesn't get the "are offline" messages :P
[13:38] <fginther> Saviq, yes, i386-3 is. I'll get it updated and back online in a few minutes
[13:38] <Saviq> fginther, right, nothing that involves us, we're using amd64 :)
[13:38] <fginther> Saviq, yes, the amd64 ones are all enabled
[13:39] <mzanetti> Saviq: FYI: we're using i386 for mediumtests
[13:39] <Saviq> mzanetti, yeah, ok, I was looking at qmluitests
[13:49] <nic-doffay> Saviq, kgunn the music scope in that link?
[13:49] <nic-doffay> All I see is the option selector!
[13:49] <Saviq> nic-doffay, what are you looking for in that spec?
[13:50] <Saviq> nic-doffay, just put some dummy data in
[13:50] <kgunn> nic-doffay: i think that's people
[13:58] <tsdgeos> Saviq: so i fixed the show header thing, but the test is extremely unstable when run against 5.0 (works fine against my self compiled 5.1)
[13:59] <tsdgeos> what do we do? commit the fix with the test commented?
[13:59] <Saviq> tsdgeos, yes please
[13:59] <tsdgeos> ok
[13:59] <dednick> larsu: ping
[14:00] <larsu> dednick: ähi
[14:00] <larsu> ugh, stupid ä key
[14:01] <dednick> larsu: :) hey. having a bit of troulble with the indicators-client autopilot tests on jenkins.
[14:02] <dednick> larsu: the indicator-battery process doesnt run and when started, it just segfaults.
[14:02] <dednick> larsu: works on my desktop though
[14:02] <larsu> dednick: lol, we're still using indicator-battery?
[14:02] <larsu> dednick: got a backtrace?
[14:03] <mzanetti> larsu: just out of curiosity. what else would we use?
[14:04] <larsu> mzanetti: indicator-power, the one we use on the desktop. I hacked up battery before the first phone demo so that we had a battery indicator at all
[14:04] <larsu> (indicator-power wasn't compatible with the new stuff back then)
[14:04] <mzanetti> larsu: ah ok.. didn't know. is it compatible with our stuff now?
[14:04] <dednick> larsu: http://pastebin.ubuntu.com/5858481/
[14:05] <larsu> mzanetti: should be, but I don't know if it already supports the phone profile
[14:05] <dednick> larsu: doesnt look very useful
[14:05] <mzanetti> ok. thanks
[14:06] <larsu> mzanetti: doesn't look like it. But adding that to indicator-power is probably more worthwhile than fixing battery
[14:06] <dednick> larsu: no, indicator-power doesnt have a phone profile
[14:06] <larsu> dednick: ugh, no debug symbols
[14:06] <dednick> larsu: we're also using indicator-time instead of indicator-datetime
[14:06] <larsu> dednick: but a warning: "failed to query backlight devices"
[14:06] <larsu> dednick: I know, same story there
[14:07] <dednick> larsu: VM
[14:07] <larsu> these things were never meant for long time use
[14:07] <dandrader> mzanetti,  https://code.launchpad.net/~stolowski/unity8/social-preview-bindings/+merge/173041 <- that was a funny one. CI set it to "Merged" and then back to "Need Review" :D
[14:07] <mzanetti> dandrader: not entirely sure if this is really funny :D
[14:07] <larsu> dednick: where does the latest code for indicator-battery live?
[14:08] <dednick> larsu: indicator-power/phablet i think
[14:08]  * larsu has a vague recollection of putting it into some +junk branch
[14:08] <larsu> dednick: thanks
[14:10] <FernandoMiguel> howdy
[14:10] <FernandoMiguel> anyone can point me in the direction of debugging unity ?
[14:10] <FernandoMiguel> doing $ killall -9 unity-panel-service every few minutes, is no longer an option :(
[14:10] <mzanetti> fginther: I think we need the local repository also for ci, not only autolanding. Could you enable that for us?
[14:11] <FernandoMiguel>   Installed: 7.0.2+13.10.20130705.1-0ubuntu1 on ubuntu 13.10
[14:11] <fginther> mzanetti, hmm, that should be also work
[14:11] <fginther> mzanetti, hmmm
[14:12] <mzanetti> fginther: oh... not sure where I was looking
[14:12] <mzanetti> seems there, yes. sorry for the noise
[14:14] <larsu> dednick: that brightness warning seems to be the issue. Whoever wrote that code doesn't check for NULL in the case that the brightness devices can't be found
[14:14] <dednick> larsu: ah. i c
[14:15] <larsu> dednick: I'll cook up a patch if you'll test it ;)
[14:15]  * larsu doesn't have a device for testing set up right now
[14:16] <dednick> larsu: sure. i'll have to test it on jenkins though
[14:17] <tsdgeos> mzanetti: can you verify https://code.launchpad.net/~aacid/unity8/fixShowHeaderHalfShownAtTop/+merge/173727 fixes the bug for you?
[14:18] <mzanetti> tsdgeos: on it
[14:20] <tsdgeos> cool
[14:20] <tsdgeos> greyback_: if you can have a look too
[14:22] <Saviq> mzanetti, gentle reminder:
[14:22] <Saviq> dh_install: usr/share/unity8/plugins/mocks/Unity/Launcher/qmldir exists in debian/tmp but is not installed to anywhere
[14:22] <Saviq> dh_install: usr/share/unity8/plugins/mocks/Unity/Launcher/libMockLauncherPlugin.so exists in debian/tmp but is not installed to anywhere
[14:22] <greyback_> tsdgeos: couldn't you use QSKIP() instead of commenting it all out?
[14:23] <mzanetti> Saviq: yep... just seen it and running a build
[14:23] <tsdgeos> greyback_: i can, want me to?
[14:23] <greyback_> tsdgeos: and what bug it it? Could you attach it to the MR please?
[14:23] <tsdgeos> mzanetti: did you open a bug?
[14:24] <mzanetti> tsdgeos: no
[14:24] <greyback_> tsdgeos: I'd prefer it, as you get "Skip" prints to remind you the test was skipped.
[14:24] <tsdgeos> greyback_: ↑↑
[14:24] <Saviq> greyback_, scroll so that thick separator is half-on screen, scroll to the sides
[14:24] <greyback_> thanks
[14:24] <Saviq> greyback_, → full breakage
[14:24] <Saviq> it's starts to behave like The Incredible Machines
[14:27] <Saviq> dednick, hey, you getting anywhere with autopilot?
[14:27] <nic-doffay> Saviq, does the expandable item only exist for pre expanded lists?
[14:28] <Saviq> nic-doffay, rephrase please
[14:28] <dednick> Saviq: yep. jenkins is using a vm which has no backlight interface, causing the battery indicator to crash and test to fail. larsu fixing up a patch for me to test.
[14:28] <dednick> Saviq: can reproduce on local VM
[14:28] <Saviq> dednick, awesome
[14:29] <Saviq> nic-doffay, if you mean contained vs. full-width; expanding vs. expanded, all 4 combinations should be possible
[14:29] <nic-doffay> Saviq, that's what I meant.
[14:30] <nic-doffay> Saviq, you would the expanding option be treated with mouse clicks though?
[14:30] <nic-doffay> If an item is expanded then it shouldn't be able to be selected and collapse the list...
[14:30] <Saviq> nic-doffay, if "expandable: false", you can't collapse
[14:31] <nic-doffay> Saviq, that's what I meant so it will only be available for non-expandable lists?
[14:31] <Saviq> nic-doffay, collapsing? yes
[14:32] <Saviq> nic-doffay, but expandable: false is just a simple constraint on top of the regular expandable
[14:32] <Saviq> nic-doffay, which results in it being always full-height
[14:32] <nic-doffay> Saviq, yeah.
[14:33] <nic-doffay> but that's not what I meant.
[14:33] <nic-doffay> I'm probably not explaining myself properly.
[14:33] <nic-doffay> Imagine this scenario:
[14:33] <nic-doffay> There is an entire list which is collapsible. If it's full of expanding items would the only way to collapse the list be to select the header one?
[14:34] <nic-doffay> Thinking of the OptionSelector right now.
[14:35] <nic-doffay> Which would be full of expanding icons.
[14:35] <nic-doffay> Saviq, because at the moment the option selector selects options.
[14:36] <nic-doffay> It's a bit counter intuitive if that feature is disabled in it imo.
[14:36] <Saviq> nic-doffay, no, tapping outside of the item would collapse it, too
[14:36] <Saviq> nic-doffay, and according to the spec actually scrolling the view would, too
[14:37] <nic-doffay> Saviq, cool I'll read it closer.
[14:50] <tsdgeos> Saviq: the thing that installs the dependencies .deb when running ./build wants me to remove libunity-scopes-json-def-desktop and install libunity-scopes-json-def-phone
[14:51] <tsdgeos> i've said no :D
[14:51] <Saviq> tsdgeos, you can install it
[14:51] <Saviq> tsdgeos, it's just used build-time
[14:51] <dandrader> greyback_,  do you know where /system/bin/ubuntuappmanager comes from?
[14:51] <dandrader> (the repo)
[14:51] <tsdgeos> Saviq: ah
[14:52] <greyback_> dandrader: sorry no. That's inside the android chroot, no idea where that comes from. sergiusens?
[14:53] <dandrader> greyback_, yes, it's in the chroot
[14:53] <tsdgeos> it's from the qt-ubuntu thing, no?
[14:53] <tsdgeos> ricmm should know afair
[14:54] <dandrader> tsdgeos, no, qtubuntu is the qt platform abstraction plugin. ubuntuappmanager is the process that talks to surfaceflinger to manipulate stacking etc AFAIU
[14:54] <greyback_> tsdgeos: nope, nothing to do with qtubuntu. That's ubuntu side
[14:54] <tsdgeos> ok
[14:54] <tsdgeos> still i'd ask ricmm :D
[14:56] <tsdgeos> greyback_: ok, QSKIPed the test
[14:57] <greyback_> tsdgeos: thanks.
[14:59] <tsdgeos> greyback_: it's even a smart QSKIP!
[15:00] <larsu> dednick: sorry for the delay, was distracted. Patch is here: https://code.launchpad.net/~larsu/indicator-power/phablet-fix-brightness-crash
[15:02] <larsu> dednick: and a MR: https://code.launchpad.net/~larsu/indicator-power/phablet-fix-brightness-crash/+merge/173747
[15:03] <dednick> larsu: ta. will take a look
[15:17] <FernandoMiguel> is there any # for user support?
[15:19] <mzanetti> FernandoMiguel: I think you're in the correct channel. But we unity8 people spam the channel so much that unity7 question might drown in the noise :/
[15:20] <FernandoMiguel> mzanetti: I assume 8 is the next version? I'm on 13.10 :S
[15:20] <mzanetti> FernandoMiguel: yeah. the phone+tablet+dekstop thing
[15:20] <FernandoMiguel> okat
[15:20] <FernandoMiguel> anyone I can bug about this?
[15:20] <FernandoMiguel> I should affect more users as they join 13.10 testing
[15:21] <Saviq> nic-doffay, https://code.launchpad.net/~saviq/unity8/improve-openeffect/+merge/173750
[15:21] <mzanetti> FernandoMiguel: usually unity7 people are around too. but I haven't seen one of them today yet
[15:21] <FernandoMiguel> :(
[15:21] <nic-doffay> Saviq, will get to it soon.
[15:21] <Saviq> nic-doffay, k
[15:21] <FernandoMiguel> tips on how to debug it so I can at least file a bug?
[15:21] <FernandoMiguel> cause saying: it's eating one core, aint enough
[15:21]  * mzanetti has absolutely no clue about unity7
[15:21] <FernandoMiguel> LOL
[15:22] <FernandoMiguel> had no idea it changed so much
[15:22] <FernandoMiguel> guess you guys need a new $
[15:22] <FernandoMiguel> *#
[15:22] <mzanetti> FernandoMiguel: its a rewrite. in a differnt language :)
[15:23] <mzanetti> tsdgeos: hey, do you think we could somehow suppress the -Wpedantic warnings coming from the private Qt includes used in LVWPH?
[15:23] <mzanetti> tsdgeos: I'm always worried they hide real ones
[15:23] <tsdgeos> mzanetti: drop the -Wpedantic? :d
[15:23] <mzanetti> tsdgeos: I'm thinking more about #pragma push  etc
[15:23] <mzanetti> but I never used that with gcc
[15:24] <tsdgeos> mzanetti: same here, no pragma magic on my side
[15:24]  * mzanetti thinks back to the dark days when he had to use msvc :D
[15:24] <tsdgeos> but i can see what mr google says
[15:26] <tsdgeos> #pragma GCC diagnostic push
[15:26] <tsdgeos> #pragma GCC diagnostic ignored "-pedantic"
[15:26] <tsdgeos> seems should work
[15:26] <tsdgeos> let's see
[15:27] <mzanetti> tsdgeos: yeah, need to #pragma pop it again. just wrap the #include in this. should do
[15:27] <dednick> larsu: 18	+    devices = g_udev_client_query_by_subsystem (client, "bcklight");
[15:27] <tsdgeos> sure
[15:27] <dednick> larsu: did you mean to change to bcklight from backlight?
[15:27] <greyback_> tsdgeos: approved, will wait for CI before top approving
[15:28] <larsu> dednick: woah, of course not. I used that to reproduce the crash. Thanks for catching it :)
[15:28] <Saviq> nic-doffay, I had to resubmit with a prerequisite https://code.launchpad.net/~saviq/unity8/improve-openeffect/+merge/173752
[15:28] <dednick> larsu: :)
[15:28] <tsdgeos> is anyone else getting this?
[15:28] <tsdgeos> QFontDatabase: Cannot find font directory '/usr/lib/x86_64-linux-gnu/fonts' - is Qt installed correctly?
[15:28] <tsdgeos> Mirv: ↑↑ ?
[15:28] <Saviq> tsdgeos, yeah, all of us are getting that
[15:29] <tsdgeos> ok
[15:29] <Saviq> tsdgeos, it's qmlplugindump or whatever
[15:29] <tsdgeos> that's new isn't it?
[15:30] <larsu> dednick: pushed a patch. Embarrassing :P
[15:30] <dednick> larsu: cool. happens to everyone :)
[15:31] <Saviq> tsdgeos, yes, dednick added the qmltypes thingie recently
[15:31] <tsdgeos> aah
[15:31] <Saviq> Mirv, but yeah, it might be interesting to you, too, just run `qmlplugindump Foo 1` and it will spew out the fonts not found error
[15:33] <tsdgeos> mzanetti: https://code.launchpad.net/~aacid/unity8/disablePedanticQtPrivateHeaders/+merge/173755
[15:34] <nic-doffay> Saviq, k
[15:36] <mzanetti> tsdgeos: perfect
[15:42] <larsu> dednick: is that branch set up for automerging?
[15:42] <dednick> larsu: i have no idea
[15:43] <dednick> larsu: probably not
[15:43] <larsu> dednick: ya, that's what I'm thinking as well. I'll merge it manually
[15:44] <dednick> larsu: actually, it has jenkins ci runs on a previous merge
[15:44] <larsu> dednick: oh okay. I'll wait a bit then :)
[15:49] <dednick> larsu: will it automatically be uploaded to the phablet-team ppas? or is a manual trigger?
[15:49] <dednick> i'm guessing manual
[15:49] <larsu> dednick: no clue, probably manual, yes
[16:06] <kenvandine> fginther, when making changes to autolanding in cu2d-config, do you need to update something in jenkins?
[16:06] <kenvandine> fginther, can you look at https://code.launchpad.net/~ken-vandine/cupstream2distro-config/autoland_friends-app_sdk/+merge/173718
[16:06] <fginther> kenvandine, we usually need to re-deploy the jobs
[16:07] <kenvandine> that's it though?
[16:07] <kenvandine> i can do that :)
[16:07] <kenvandine> or is there another redeploy that you need?
[16:09] <fginther> kenvandine, nope, just the one. Are you using the deploy-cupstream2distro-config job?
[16:09] <kenvandine> no
[16:09] <kenvandine> cu2d-update-stack
[16:09] <fginther> update-stack does not deploy the jobs to s-jenkins
[16:10] <kenvandine> ah
[16:10] <fginther> kenvandine, you would need to use cu2d-update-ci
[16:10] <fginther> or just use the jenkins job :-)
[16:10]  * kenvandine doesn't know how to do either... maybe i shouldn't know :)
[16:35] <nic-doffay> Saviq, so I'm assuming the OptionSelector should also have a variable delegate?
[16:35] <nic-doffay> Or just an expandable delegate which is set to either true or false?
[16:35] <Saviq> nic-doffay, that's a design question
[16:35] <nic-doffay> Saviq, ok so nothing has been decided on yet.
[16:35] <Saviq> nic-doffay, I'd assume icon + text
[16:35] <Saviq> nic-doffay, unless I don't understand your question
[16:36] <Saviq> icon optional
[16:36] <nic-doffay> Saviq, k
[16:46] <Mirv> Saviq: yeah it has always spewn out that, I haven't seen a configure option that would affect it
[16:46] <Saviq> Mirv, k
[16:46] <Mirv> tsdgeos dropped from the channel it seems
[16:47]  * Mirv -> night
[16:50] <mzanetti> Saviq: do we store the stdout somewhere on the device?
[16:50] <Saviq> mzanetti, ricmm should know
[16:50] <Saviq> mzanetti, I think we do
[16:51] <greyback_> mzanetti: yes in ~.ubuntu-session or ~.ubuntu-touch-session
[16:52] <mzanetti> greyback_: cheers
[16:54] <mzanetti> om26er: replied to the bug
[16:55] <Saviq> fginther, /me no get it http://s-jenkins:8080/job/unity8-autolanding/54/ http://s-jenkins:8080/job/unity8-autolanding/55/
[16:55] <Saviq> fginther, 54 landed https://code.launchpad.net/~paulliu/unity8/fix-video-lens/+merge/173674
[16:55] <Saviq> fginther, it's in trunk https://code.launchpad.net/~unity-team/unity8/trunk
[16:55] <Saviq> fginther, but it's merging once more in 55?
[16:56] <Saviq> fginther, and the branch isn't updated that it's Merged, and the changelog entry doesn't contain the "Merged branch lp:xxx" thing...
[16:56] <fginther> Saviq, looking
[16:59] <om26er> mzanetti, thanks. I commented some stuff
[17:00] <fginther> Saviq, possibly it was merged by hand?
[17:01] <Saviq> fginther, ah
[17:01] <Saviq> fginther, http://s-jenkins:8080/job/unity8-autolanding/54/console
[17:01] <om26er> to keep upto date should I still flash the newest saucy-preinstalled-touch-armel+mako.zip or is that now covered with apt-get dist-upgrade ?
[17:01] <Saviq> fginther, http://10.97.2.10:8080/job/phablet-land/1215/console
[17:01] <Saviq> fginther, or is that ok?
[17:01] <fginther> Saviq, I'm looking through the jenkins logs.
[17:02] <mzanetti> mterry: any idea on this? https://bugs.launchpad.net/unity8/+bug/1199441
[17:02] <Saviq> fginther, shouldn't have been merged manually
[17:02] <mzanetti> om26er: I flash all the time...
[17:03] <fginther> Saviq, by the time 54 finished, lp:unity8 had already been updated
[17:03] <Saviq> fginther, interesting...
[17:03] <fginther> Saviq, 55 is running because of the incorrect status on the merge proposal
[17:04] <Saviq> fginther, so maybe http://s-jenkins:8080/job/unity8-autolanding/53/parameters/? merged it?
[17:04] <Saviq> probably not
[17:04] <Saviq> fginther, ok, nvm, let's see what happens
[17:05] <fginther> Saviq, I'll dig a little more, just in case the jenkins tools have a bug
[17:05] <Saviq> fginther, thanks
[17:38] <dednick> Saviq: ping
[17:38] <Saviq> dednick, pong
[17:39] <dednick> Saviq: howdy. larsu has fixed the bug in indicators-battery and it's been merged. we need to get it into the ppas.
[17:40] <dednick> Saviq: do we need to bump the version or something?
[17:43] <Saviq> dednick, it's daily-released, right?
[17:44] <Saviq> dednick, so we probably should just wait for it to release, and that's it
[17:49] <dednick> Saviq: I have no idea if it's daily-released. where can i check?
[17:50] <Saviq> dednick, in debian/changelog of it
[17:50] <dednick> Saviq: actually, it's a bit of a hack branch of indicators-power, in lp:indicators-power/phablet
[17:51] <Saviq> dednick, http://bazaar.launchpad.net/~indicator-applet-developers/indicator-power/phablet/view/head:/debian/changelog
[17:51] <Saviq> dednick, it needs to be bumped-released, right sergiusens?
[17:52] <Saviq> dednick, so you need to MP a debian/changelog bump for saucy
[17:52] <Saviq> dednick, so that http://s-jenkins:8080/job/indicator-power-phablet-autolanding/ kicks in
[18:01] <mterry> mzanetti, looking
[18:01] <mzanetti> mterry: I haven't seen this before
[18:01] <mterry> mzanetti, weird, nor have i
[18:01] <mzanetti> mterry: could it be because he only dist-upgrades instead of flashing?
[18:01] <mterry> mzanetti, don't know why it would be
[18:02] <mzanetti> mterry: shouldn't... but who knows
[18:02] <mterry> mzanetti, not even sure how that would happen.  either the power button signal or the greeter.show() wouldn't be working for him
[18:03] <mzanetti> mterry: what if the lightdm plugin doesn't load? I guess that would prevent the shell from starting already
[18:04] <dednick> Saviq: how do you generate the changelog entry from bzr history? manual or is there an automated tool?
[18:04] <Saviq> dednick, I bet there's some tool, I just never remember what it is :)
[18:05] <dednick> Saviq: :) yeah, i'm guessing the daily-release does it somehow. nevermind. will just manual it.
[18:05] <mterry> mzanetti, yeah, I would bet
[18:05] <Saviq> dednick, there's "debcommit" but it actually works the other way 'round
[18:06] <Saviq> mterry, bzr log → debian/changelog, any tool?
[18:06] <Saviq> dednick, yeah, I believe that's a custom tool, though
[18:08] <mterry> Saviq, I've never used one, always the other way with debcommit
[18:08] <mterry> Saviq, but I bet didrocks built something for his daily release stuff
[18:08] <Saviq> mterry, that's what I thought, thanks
[18:09] <dednick> Saviq: http://pastebin.ubuntu.com/5859125/ ? look right to you?
[18:09] <dednick> not sure about the version
[18:09] <Saviq> dednick, I'd probably continue the previous scheme, so 13.10.1phablet1
[18:10] <dednick> Saviq: I think it's the the .1 is the month after of the release.
[18:12] <dednick> Saviq: so it'd have to be a 13.10.-3 ;)
[18:13] <Saviq> dednick, TBH if it's higher - it's good!
[18:21] <dednick> Saviq: https://code.launchpad.net/~nick-dedekind/indicator-power/phablet.release.bump/+merge/173785
[18:23] <Saviq> dednick, for the sake of being picky, can you please revert the whitespace change?
[18:23] <dednick> Saviq: sure
[18:24] <dednick> Saviq: harder than you think when you have save removing the whitespace in your editor :)
[18:24] <Saviq> dednick, I know! ;D
[18:24] <Saviq> dednick, uncommit, shelve, commit ;)
[18:33] <dednick> Saviq: done
[18:34] <Saviq> dednick, thanks
[19:04] <Saviq> fginther, ugh... unity8-autolanding seems to take an hour now (1/2h before), is that expected? or maybe just queue?
[19:05] <fginther> Saviq, the armhf queue is really long right now, that's probably the issue.
[19:06] <Saviq> fginther, ok
[19:56] <fginther> Saviq, I did find a jenkins tools bug related to the weird commit. Rolling out the fix now.
[19:56] <Saviq> fginther, thanks
[21:16] <Saviq> mzanetti, can you `bzr commit --unchanged` launcher-backend and push so that jenkins picks it up with the scheduler?
[21:16] <Saviq> mzanetti, it feels like it's been rebuilt too many times now and it's not really doing the right thing
[21:17] <mzanetti> Saviq: nah. I just manually killed the job and re-triggered it because it was again on a non updated panda
[21:17] <mzanetti> Saviq: I'm currently walking through all pandas and upgrading the hooks
[21:18] <mzanetti> Saviq: ok. last one done. the hooks issue should be gone for good now
[21:19] <Saviq> mzanetti, thanks
[22:01] <mzanetti> Saviq: I wonder why the DashBar test started failing in jenkins
[22:11] <Saviq> mzanetti, did you see more than one failure?
[22:12] <mzanetti> Saviq: 7 in a row
[22:12] <mzanetti> Saviq: passes locally
[22:12] <Saviq> mzanetti, ugh
[22:14] <Saviq> mzanetti, it's a 5s timeout, think it might simply be timing out?
[22:14] <Saviq> mzanetti, both tests are failing at
[22:14] <Saviq> tryCompare(panel, "animating", false) // wait till the animation ends
[22:14] <Saviq> mzanetti, unless something changed in the sdk...
[22:14] <mzanetti> Saviq: no... its the compare() above
[22:15] <mzanetti> ah no
[22:16] <Saviq> last toolkit release was 16h ago, so not that
[22:18] <mzanetti> Saviq: uh... after upgrading my machine it fails locally
[22:18] <mzanetti> same failure
[22:18] <Saviq> mzanetti, what did you upgrade?
[22:18] <mzanetti> http://paste.kde.org/792728
[22:18] <Saviq> yeah, it's the SDK for sure
[22:19] <Saviq> will pinpoint the rev if can reproduce
[22:23] <Saviq> mzanetti, it's the last commit in the toolkit
[22:23] <mzanetti> Saviq: and its a but in the panel
[22:23] <mzanetti> the "animating" property goes once to true and never back to false
[22:23] <mzanetti> good we're testing their stuff
[22:24] <mzanetti> why do I keep on writing "but" instead of "bug"?
[22:26] <mzanetti> Saviq: should I report a bug or are you already taking action?
[22:27] <Saviq> mzanetti, I'll file, can you find out where we've picked the new SDK from? so that we can disable it for the time being, maybe?
[22:28] <mzanetti> Saviq: Get: 4 http://ppa.launchpad.net/ubuntu-sdk-team/ppa/ubuntu/ saucy/main qtdeclarative5-ubuntu-ui-toolkit-plugin amd64 0.1.46+13.10.20130709bzr600saucy0 [257 kB]
[22:28] <mzanetti> Saviq: is it actually still a good idea to use that ppa?
[22:28] <mzanetti> probably not
[22:28] <Saviq> mzanetti, if it's daily released anyway, probably not
[22:36] <mzanetti> Saviq: ppa is removed and the 3 jobs retriggered. I'm off for bed... see you tomorrow.
[22:36] <Saviq> mzanetti, thank you, cheers