[00:07] <Elleo> nik90: cool :)
[00:14] <kenvandine> Elleo, hey
[00:14] <kenvandine> you're here :)
[00:15] <kenvandine> Elleo, mzanetti has an awesome new imgur share handler :)
[00:16] <kenvandine> Elleo, works great, however his ContentPeerPicker has a black line below the header, instead of gray
[00:16] <kenvandine> only seeing it when the peer picker is shown in his app
[00:17] <Elleo> kenvandine: odd :/
[00:17] <Elleo> kenvandine: mostly falling asleep at the moment, I'll give it a try tomorrow and see if I can see anything obvious
[00:17] <kenvandine> i know you fixed some theme stuff there
[00:17] <kenvandine> http://bazaar.launchpad.net/~mzanetti/imgur-share/trunk/view/head:/app/Main.qml
[00:17] <kenvandine> Elleo, sure, thanks!
[00:17] <Elleo> no worries :)
[00:18] <kenvandine> i was surprised to see you up :)
[00:18] <Elleo> yeah, just got home and was checking hilights before heading to bed :)
[00:19] <kenvandine> Elleo, good night!
[00:19] <Elleo> night :)
[06:00] <akiva-thinkpad> !ping
[06:39] <zsombi_> charles: nik90: in continuation on yesterday's alarm snooze discussion: noone said the apps should fully use the flexibility a service provides. Alarm service will provide flexible setup, and apps can decide whether they use that or not. It would be opposite, if the API would restrict their hands, and then we'd get complaints that teh API is too restrictive
[07:05] <akiva-thinkpad> morning all
[08:12] <dholbach> good morning
[08:41] <dholbach> mhall119, looks like bug 1435759 is getting some movement - thanks Mirv!
[08:42] <Mirv> dholbach: it'd be ready, but we'd need arhive admin to review the new binary packages from the PPA, which is a bit weird for them. the reason is that publishing would bypass binNEW queue.
[08:42] <Mirv> dholbach: I've asked on #ubuntu-release a few hours ago
[08:42] <dholbach> right
[08:42] <Mirv> mhall119 already got the docs from the PPA yesterday for testing
[08:43] <dholbach> excellent :-D
[08:44] <dpm> thanks a lot Mirv!
[08:46] <akiva-thinkpad> bzoltan_, zbenjamin any update? Anything you want from me? Also I moved the owners of that project to the sdk team, so you can now merge at your liesure.
[08:47] <Mirv> you're welcome
[08:48] <bzoltan_> akiva-thinkpad:  is the segfault fixed now?
[08:48] <akiva-thinkpad> bzoltan_, yes
[08:48] <akiva-thinkpad> fixed, merged with your branch, and pushed to trunk
[08:49] <bzoltan_> akiva-thinkpad: sweet :) let me check the code then. zbenjamin will tell the last word next week
[08:50] <akiva-thinkpad> Sure
[12:07] <dpm> nik90, Elleo, not bad, podbird now translated in 14 languages :)
[12:07] <Elleo> dpm: yep, awesome :)
[12:08] <Elleo> dpm: I'll try to put out a release this weekend so people can start enjoying the translations
[12:08] <dpm> nice :)
[12:11] <dee_> hi, know someone how to use the 'data-role="actions"' in html5 correct?
[12:12] <daker> dee_: automaticaly for now, they generated on the fly
[12:13] <nik90> dpm: indeed..it looks awesome
[12:14] <dee_> y saw that in the debug output, but i need now a own icon in the header
[12:15] <dee_> thats just dont look well: http://pastebin.ubuntu.com/10688709/
[12:23] <dee_> daker any idea?
[12:24] <daker> dee_: are you using tabs ?
[12:26] <dee_> no not on this page
[12:26] <dee_> there i need the actions
[12:26] <dee_> but mb i need later on my tab page some actions too ...
[12:45] <dee_> ok thats a "bug" in the tabs.scss
[12:45] <dee_> its need a         width: units_gu(5);         height: units_gu(7.5);
[12:45] <dee_> then its work better
[12:46] <daker> dee_: you can reports bugs here https://launchpad.net/ubuntu-html5-theme
[12:59] <dee_> the whole html5 "theme" seems bugy ... sometimes my action comes after 10 sec, sometimes the backbutton is not there ...
[13:03] <dee_> but ok i see the ubuntu phone still in a beta
[13:14] <Elleo> kenvandine: had a quick look at the black header separator, seems to only happen with Ubuntu.Content 1.1 (which uses the new Header style); I'm guessing something changed in the way the UITK figures out the appropriate colouring for the separator. I've filled a bug here for now: https://bugs.launchpad.net/content-hub/+bug/1437307 will try to look into it more when I have some time spare
[13:18] <balloons> dholbach, I missed your morning greetings of a code review!
[13:19] <dholbach> balloons, yeah, I had a few other things to do and didn't manage to fix the bug yet
[13:19] <dholbach> balloons, if you want, you can ask me for a code review for help-app? :)
[13:19] <balloons> dholbach, :-) I was going to ask you to do a review of my stuff
[13:21] <balloons> dholbach, if you don't mind having a quick look at https://developer.ubuntu.com/en/scopes/tutorials/scopes-unit-testing/, I'd appreciate your C++ insights: https://developer.ubuntu.com/en/scopes/tutorials/scopes-unit-testing/
[13:23] <dholbach> balloons, I think it'd be better to require 14.10
[13:23] <dholbach> balloons, that'll give you the scope runner and stuff for writing scopes locally
[13:23] <dholbach> I'd also link to https://developer.ubuntu.com/en/start/ubuntu-sdk/ or some such
[13:23] <balloons> ack, changing.. I also see another little mistake to fix
[13:24] <dholbach> so people install the SDK first
[13:25] <kenvandine> Elleo, thx!
[13:25] <dholbach> balloons, "sudo cp libg*.a /usr/lib/" ??
[13:25] <dholbach> seriously?
[13:25] <dholbach> I really don't think we should ask people to manipulate /usr
[13:26] <dholbach> why is this necessary?
[13:27] <balloons> dholbach, that was something I wanted your opinion on for sure, glad you picked up on it
[13:28] <dholbach> ok cool
[13:28] <dholbach> don't we ship this library somewhere else?
[13:28] <dholbach> how do other c++ tests in our projects do it?
[13:28] <balloons> So apparently we don't package libgtest and instead we only ship source. people have to compile it (of which there are a few different ways)
[13:28] <dholbach> hum
[13:28] <balloons> We don't ship the lib directly because they asked us not to do so
[13:29] <dholbach> the thing is... whenever we fix a bug in libgtest-dev in the archive, people will still have the buggy version in /usr installed
[13:30] <balloons> right.. so it's REALLY wild how it works. Plus I would really rather they build and push the lib somewhere locally rather than mucking around in /usr if they had to do it this way
[13:30] <balloons> overall though, it seems odd
[13:30] <dholbach> yep, I agree - it'd be great if that wasn't necessary
[13:30] <balloons> see https://code.google.com/p/googletest/wiki/FAQ#Why_is_it_not_recommended_to_install_a_pre-compiled_copy_of_Goog
[13:31] <dholbach> maybe we can ask folks on c-tech or u-phone for how they do their testing?
[13:31] <balloons> dholbach, so I was thinking of crafting the cmake file to pull the library automatically and use it
[13:32] <balloons> that way it's all local to the project. But it requires you to setup your cmake file, and of course use cmake
[13:32] <dholbach> like... copy /usr/src/gtest into the source tree and use it from there?
[13:32] <balloons> dholbach, cmake can actually pull the source tarball and set it up for local build..
[13:32] <dholbach> that's like how config.guess and stuff also make it into projects
[13:33] <balloons> so that would be outside of the package archive.. pulling from google itself
[13:33] <dholbach> but yeah, I think I'd ask folks in the relevant upstream teams how they do it
[13:33] <dholbach> and derive "best practices" from that :)
[13:34] <balloons> I've not asked everyone, but thus far it seems this is how it's done
[13:34] <balloons> what do you personally think of the cmake idea.. let me throw a snippet at you
[13:35] <dholbach> how about asking somebody like sil2100? he's on the foundations team and he has way more experience with cmake and stuff than I do :)
[13:35] <dholbach> but sure, I can take a look
[13:36] <dholbach> maybe link to https://developer.ubuntu.com/api/scopes/sdk-14.10/unity.scopes.testing/ from somewhere as well
[13:37] <balloons> something like http://paste.ubuntu.com/10689076/?
[13:37] <balloons> but yea, I'm no cmake expert. I'm just curious about opinions on doing it that way vs installing the -dev package and compiling
[13:37] <dholbach> did davidcalle look over this too?
[13:38] <nik90> zsombi_: Can you check with bzoltan_ if it would be possible to land the new alarmId property and the find() method in Ubuntu.Components 1.2? Considering that the necessary bits will land in indicator-datetime and qtorganizer5-eds in vivid, it would be nice to see this in 1.2.
[13:38] <balloons> no, not yet
[13:38] <nik90> s/check/discuss
[13:38] <zsombi_> nik90: I will
[13:38] <dholbach> he's our local scopes expert :)
[13:38] <nik90> zsombi_: thnx
[13:38] <dholbach> I'm sure he'll have more ideas than I do
[13:39] <dholbach> maybe we could also explain in a sentence or two what the fixture class does and which parts of the setup it deals with?
[13:39] <dholbach> (I have never heard of it before :))
[13:43] <dholbach> and maybe link to a few examples of scopes with tests?
[13:43] <dholbach> a lot of developers will likely want to copy/paste :)
[13:43] <dholbach> .... and then fix the breakage by reading the bits in the doc
[13:43] <dholbach> ... which reads very nicely
[13:45] <balloons> dholbach, excellent points. Full Examples are a bit harder to find atm, but would be useful. I'll add something to intro the test fixtures class a bit more
[13:45] <zsombi_> kalikiana: t1mp: https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/expose-alarm-id/+merge/254084
[13:45] <dholbach> balloons, maybe just link to the bzr branches?
[13:46] <balloons> dholbach, that's a good idea as the docs is already long enough without inlining more code
[13:46] <dholbach> yep :)
[13:46] <dholbach> good work
[13:56] <t1mp> zsombi_: https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/headlock/+merge/253845 :)
[14:08] <kalikiana> t1mp: you need to update components.api https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/35-tstHeaderActions/+merge/254228
[14:15] <charles> zsombi_, which feature are you referring to?
[14:16] <t1mp> kalikiana: done. Actually I needed to update it in the prerequisite. For some reason  Page 1.3 was twice in the components.api, I don't know why
[14:16] <charles> zsombi_, the variable alarm durations?
[14:32] <t1mp> kalikiana: where does an Item with MainView as a child not work?
[14:33] <t1mp> kalikiana: we do that with most tests in unit_x11
[14:33] <t1mp> maybe all
[14:33] <t1mp> ah no not all, only those that need a MainView
[14:33] <kalikiana> t1mp: yeah, for most tests it's fine, but we get the root item in a few cases, for example pop overs when checking automaticRotation
[14:34] <kalikiana> that won't work
[15:01] <charles> renatu, popey, zsombi_, nik90, the datetime/qorganizer changes are in silo 8
[15:01] <renatu> charles, nice thanks
[15:02] <nik90> charles: thnx. I will keep track of the silo status.
[16:07] <dpm> dholbach, balloons, so why is it necessary to build googletest locally in the scopes testing tutorial?
[16:07] <dholbach> dpm, https://code.google.com/p/googletest/wiki/FAQ#Why_is_it_not_recommended_to_install_a_pre-compiled_copy_of_Goog
[16:07] <dholbach> balloons enlightened me there :)
[16:09] <balloons> dpm, right. I'm leaning pretty heavily towards putting it in cmake and letting the project build and worry about it locally. But I really do wish we could simply use the package sanely
[16:09] <balloons> I feel like copying it into /usr/lib isn't the best idea
[16:15] <nik90> balloons: How often are the jenkins machines updated? (Just to know if they have got the latest SDK installed)
[16:16] <dpm> balloons, no, me neither, app developers shouldn't have to hack the platform to test
[16:18] <balloons> nik90, they repull depends each time. So they should always be up to date as it where I believe
[16:19] <nik90> balloons: ack.
[16:19] <balloons> dpm, polling some more folks for opinions and options :-)
[16:20] <dpm> balloons, good idea. So if it's just about the compiler flags, could the cmake file not just replicate the google test lib compile flags
[16:21] <dpm> (says not-so-much-of-a-c++-expert-dpm naively)
[16:23] <balloons> dpm, that was the big fear for not packaging the thing to begin with.
[16:24] <balloons> So I feel like the solution is to grab them for each project and let the compiler automagically compile them with the same flags
[16:24] <dpm> oh, so there is no package for googletest?
[16:24] <balloons> but I'm with you on the c++ thing.. I learned it first and used it little since :-)
[16:24] <balloons> dpm, no, only the -dev package. It was purposefully removed because of the compiler issue
[16:24] <dpm> ok
[16:25] <dpm> so, can it not be built locally as part of the scope project, rather than put it in /usr/lib?
[16:27] <balloons> dpm, of course it can. That was the cmake idea. I guess perhaps a third option of not using cmake to install the library, but instead grab it from the -dev package and compile it?
[16:29] <zsombi_> charles: yes, I was talking about that.
[16:30] <balloons> dpm, I think I'll push that solution
[16:30] <zsombi_> charles: but I'll be back with a proposal once I'm there...
[16:32] <dpm> balloons, it might be worth asking Pete Woods too. I'm not much of an expert myself other than thinking what I said before: the more hackery app devs need to do to get the test infrastructure running, the less likely they're going to bother with tests
[16:33] <balloons> dpm, I agree.. I don't want to mess with it either. I have a working example now using cmake to build from the -dev package, which I think is the sanest option. It would be easy to not have to do it that way, but to be fair this is c++, so cmake makes sense here
[16:33] <balloons> I'm much happier with this than the /usr/lib copy :-)
[16:34] <dpm> yeah, with the disclaimer that I'm not an expert, this at least makes sense to me
[16:48] <lentzi90> Is there anything special I need to do to make ubuntu SDK detect my phone?
[16:51] <balloons> lentzi90, turn on developer mode if you haven't
[16:52] <bzoltan_> lentzi90: did it work?
[16:55] <lentzi90> bzoltan_, yes it did! I thought I read somewhere that you could activate developer mode from the SDK... I guess not :)
[16:59] <dpm> davidcalle, I guess the answer to this question is that he's out of luck? https://askubuntu.com/questions/602056/porting-ubuntu-touch-onto-toshiba-excite-at7-b01yl
[17:12] <bzoltan_> lentzi90: at the moment the device does not listen to any request unless the developer mode is enabled. That is expected to be changed at some point.
[17:13] <ogra_> bzoltan_, that will never change
[17:14] <nik90> balloons: hey, I ran https://code.launchpad.net/~nik90/ubuntu-clock-app/fixed-bottomedge-status/+merge/253998 AP tests on vivid desktop with qtdeclarative5-ubuntu-ui-toolkit-plugin version 1.2.1458+15.04.20150327-0ubuntu1 and they all pass. While this fails on jenkins due to the bottom edge not showing up.
[17:14] <ogra_> you will always have to enable developer mode .... having to unlock or having a passowrd and such will be dropped ...
[17:14] <nik90> balloons: can you confirm it on your end if you are free?
[17:14] <ogra_> once we get key auth
[17:15] <ogra_> by default no device will listen to stuff though, that will always require user interaction to enable it
[17:15] <ogra_> (once)
[17:17] <balloons> nik90, so is jenkins not running the latest or ? I'm confused a little
[17:18] <nik90> balloons: well I took your word that jenkins pulls in the latest package :) .. let me check the jenkins output logs to see if that's true
[17:19] <balloons> nik90, lol.. I guess I'm confused about what you want me to confirm / help with
[17:19] <balloons> but I am free to help now :-)
[17:19] <bzoltan_> ogra_: true.. sorry, I meant the unlock... I should EOD
[17:20] <ogra_> bzoltan_, heh, yeah, me too
[17:20] <ogra_> if that only would be that easy :)
[17:20] <bzoltan_> ogra_:  tell me about it :)
[17:20] <nik90> balloons: The MP I linked above fails on jenkins. While it passes on my up-to-date vivid laptop. I am just trying to find out why it fails on jenkins.
[17:20]  * ogra_ cant get off all the workahol ;)
[17:20] <nik90> balloons: if you run the tests on your laptop, we can confirm if it only fails on jenkins or not.
[17:22] <balloons> nik90, ahh sure. I'll run locally here and see why it might be failing (or not)
[17:23] <nik90> hmm looking at http://91.189.93.70:8080/job/generic-mediumtests-utopic/2439/artifact/dpkg-l.post.log, it seems that jenkins isn't grabbing the latest qtdeclarative5-ubuntu-ui-toolkit-plugin package.
[17:29] <balloons> nik90, well that's on utopic
[17:30]  * balloons runs
[17:35] <balloons> nik90, all the tests failed for me. So I'm running locally, app crashes.. ohh wait
[17:35] <balloons> I think I have an old copy
[17:35] <balloons> nope, never mind, r 233
[17:35] <nik90> balloons: can you paste the version of  qtdeclarative5-ubuntu-ui-toolkit-plugin ?
[17:36] <balloons> 1.2.1450+15.04.20150318-0ubuntu1
[17:36]  * balloons upgrades
[17:36] <nik90> balloons: yeah you need 1.2.1458+15.04.20150327-0ubuntu1
[17:38] <nik90> balloons: can you again give me the link to the CI docs which helps prep the phone for testing
[17:38] <bzoltan_> nik90: balloons: and that is so frash that you should watch out it does not burn your fingers
[17:38]  * balloons waits for 1.2.1458+15.04.20150327-1ubuntu1
[17:38] <balloons> :p
[17:39] <nik90> bzoltan_: :)
[17:39] <balloons> nik90, http://ubuntu-test-cases-touch.readthedocs.org/en/latest/
[17:40]  * nik90 bookmarks
[17:45]  * balloons runs again
[17:51] <balloons> Tests passed locally
[17:51]  * balloons looks at jenkins
[18:00] <nik90> popey: so the clock app crashes should be fixed now that the new UITK has landed. The only thing now left is the location-prompt AP issue. I will give it one last shot this weekend before asking QA help.
[18:00] <nik90> popey: so hopefully this Monday we can release a new clock app to the store (finally)
[18:00] <balloons> nik90, where did you get on that issue?
[18:02] <nik90> balloons: well considering that only today the crasher was fixed, only now can I actually get started on it properly
[18:02] <nik90> balloons: I could have worked on it earlier if the phone being on rtm wasn't an issue to run tests on it
[18:02] <nik90> but since it requires the latest image (vivid) the crasher was a huge blocker
[18:04] <balloons> nik90, sure. Just wanted to see if I could help in any way
[18:04] <balloons> so nik90 on the clock issue, I think we simply ask CI to move to vivid
[18:05] <nik90> balloons: yeah I can tell you more on how it goes after this weekend
[18:05] <balloons> nik90, I'm going to ask them to move it. But I guess I could trial a run first to see
[18:06] <nik90> balloons: well the crasher was introduced by the UITK package in vivid only..so may be that's not why jenkins fails?
[18:06] <nik90> balloons: let me be more descriptive'
[18:08] <nik90> balloons: so the crasher was introduced after 1.2.1450+15.04.20150318-0ubuntu1 and fixed in today's 1.2.1458+15.04.20150327-0ubuntu1 release
[18:08] <nik90> so the crasher only affected vivid (while rtm/utopic was good to go)
[18:08] <balloons> nik90, ok so in theory utopic is/was unaffected
[18:08] <nik90> balloons: yes
[18:10] <balloons> so in the videos I don't see the bottom edge at all
[18:10] <balloons> and they never get beyond that point
[18:11] <nik90> balloons: yes, that's really strange. Could it be the focus issue we had a long time back?
[18:11] <nik90> balloons: the bottom edge should show up after the alarm model is loaded and the app has focus
[18:11] <nik90> not sure which one is causing the issue
[18:39] <balloons> nik90, right right. I can run in a sandbox without the wm to simulate I ghuess
[19:07] <Canoshi> Hi all.  As anybody had the issue where the devices screen is blank in QT creator?
[19:51] <nik90> balloons: I tried running it in a sandbox without the wm and while during the test I can see the bottom edge appear, AP seems to ignore it and still fail at the clockPage.reveal_bottom_edge_page() function
[19:52] <balloons> nik90, I did the same.. it doesn't look the same as on jenkins though
[19:52] <balloons> I asked CI to do a run on vivid
[19:53] <nik90> ok
[19:53] <nik90> I am looking through the bottom edge function to see if there may be a timing issue or something
[19:58] <balloons> nik90, http://91.189.93.70:8080/job/generic-mediumtests-vivid-test/11/
[19:58] <balloons> it's running :-)
[19:59]  * nik90 keeps an eye on it
[20:00] <nik90> balloons: fyi, the sandbox run fails on trunk as well at the exact same point..so I don't think the sandbox runs helped us.
[20:01] <balloons> nik90, well it works for me in the sandbox.. that's how I tested it
[20:02] <balloons> note I am using a window manager, just like jenkins
[20:02] <nik90> balloons: ah that's probably why..I dont use a window manager..I install xserver-xephyr which autopilot3-sandbox-run used..not sure how to install a wm inside that xephyr screen
[20:10] <balloons> nik90, I use this; which I've never finished landing: https://code.launchpad.net/~nskaggs/autopilot/add-wm-sandbox-run/+merge/242274
[20:18] <nik90> balloons: oh that's smart
[20:53] <balloons> nik90, 17% tests passed, 5 tests failed out of 6
[20:54] <balloons> it didn't get to running the autopilot tests
[20:54] <nik90> balloons: did it fail the qml tests?
[20:55] <balloons> have a look http://91.189.93.70:8080/job/generic-mediumtests-vivid-test/11/consoleText
[20:55] <balloons> all the way at the bottom
[20:55] <nik90> balloons: hmm the LLVM ERROR: Cannot select: intrinsic %llvm.x86.sse41.pblendvb looks strange
[20:55] <nik90> I have never seen that before
[20:55] <balloons> yes.. it's a bit odd
[20:57] <balloons> can you toggle off the qml tests from the build and push it to a branch? I'll re-run then and we can see if the AP test situation is better or not
[20:57] <nik90> balloons: check out https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/+bug/1389729
[20:58] <nik90> looks like it is a known issue
[20:58] <nik90> sure
[21:01] <balloons> nik90, feel free to ask fginther for a re-run once disabled if I'm not around.. brb
[22:35] <SPeck84> Hy all
[22:35] <SPeck84> I trying to write my ver first application and on the begning i got some difficultys
[22:35] <SPeck84>  Sdk-Launcher> Installing the application failed
[22:35] <SPeck84> Can somabody help mepls
[22:48] <SPeck84> Is there anyone here who can help me?
[22:50] <justcarakas> Hey I'm making trying to upgrade my HTML5 app from 13.10 to 14.10 but Im getting some errors
[22:50] <justcarakas> can anybody help me with this
[22:50] <justcarakas> TypeError: this._header is null core.js:75:8 TypeError: document.styleSheets[0].addRule is not a function core.js:416:20
[22:51] <justcarakas> alex-abreu maybe ?
[22:52] <justcarakas> or daker
[23:16] <faenil> SPeck84: it's quite late friday evening, I doubt there's someone who can help :) but if you give more details about the problem maybe someone will reply tomorrow ;)
[23:21] <alex-abreu> justCarakas, have the html file for your app?
[23:23] <justCarakas> I think I found it out
[23:23] <justCarakas> i had both tab and pagestack included
[23:24] <alex-abreu> ok
[23:24] <justCarakas> can you btw still debug like you used to with debug like in the browser alex-abreu ?
[23:24] <justCarakas> I couldn't find it
[23:24] <alex-abreu> justCarakas, you should just be able to do it yes
[23:25] <alex-abreu> justCarakas, launching w/ --inspector
[23:25] <justCarakas> it used to say the ip and port
[23:25] <justCarakas> in de sdk
[23:25] <justCarakas> can I add that somewhere so it will always do that during development ?
[23:25] <alex-abreu> justCarakas, in the Exec of your desktop file
[23:26] <justCarakas> ah thx :)
[23:26] <justCarakas> the brother of a co-worker bought a BQ and told me my app was broken :p so I'll better fix it :p
[23:27] <alex-abreu> justCarakas, if you find anything ping us :) ... or report something
[23:27] <justCarakas> oke thx :)
[23:27] <justCarakas> gonne sleep now ttyl