[00:00] <nik90> ahayzen, u freaking genius! I finally got all clock AP tests passing...
[00:00]  * nik90 sighs a relief
[00:00] <ahayzen> nik90, OMG awesome man :-)
[00:00] <ahayzen> \o/
[00:01] <ahayzen> nik90, is that on jenkins though ? :')
[00:01] <nik90> ahayzen, erm no..just locally..I still need to flake and pep8 tests
[00:01] <nik90> there was a command to check that?
[00:01] <ahayzen> ah cool, and if you have location allow/deny then...
[00:01] <nik90> pyflake if I remember
[00:02] <ahayzen> i usually use $ pep8 . and $ pyflakes .
[00:02] <ahayzen> but there is $ flake8 .
[00:02] <nik90> ok
[00:02] <ahayzen> as well
[00:02] <nik90> ahayzen, I am pretty sure we resolved the location issue at some point...let's see what happens.
[00:02] <ahayzen> nik90, if you need the py3 version do $ python3 -m flake8 .
[00:02] <nik90> need to clean up the AP test file now that everything is passing and propose MP
[00:03] <nik90> hmm not sure if we converted to python3
[00:03] <ahayzen> nik90, i just wanna migrate as much as possible of ours to QUnit and then rewrite the test part of ours
[00:04] <nik90> ahayzen, so you're to use QUnit for both unit and feature testing?
[00:04] <nik90> or use both AP and QML tests?
[00:04] <ahayzen> nik90, it'll usually pass for py2 as well, just depends if you have some py3 specific syntax that fails in py2 :-)
[00:04] <ahayzen> nik90, QUnit for *as much as possible* :-) and then AP for probably more 'user stories' i would think
[00:04] <nik90> ahayzen, that's the way to go..keep user stories in AP if possible.
[00:05] <ahayzen> so really for us, we wouldn't remove many AP tests
[00:05] <ahayzen> but add loads of QUnit
[00:05] <ahayzen> however for weather... alot could be QUnit i think
[00:05] <nik90> here's thomi's post about test coverage, http://www.tech-foo.net/on-test-levels-and-coverage.html
[00:05] <nik90> +
[00:06] <ahayzen> ah cool thanks :-)
[00:06] <nik90> ahayzen, btw for weather, I migrated some of the pages to UC 1.3, thereby fixing the Silo 50 issues it had
[00:06] <nik90> still some work left for it.
[00:06] <ahayzen> nik90, awesome, i saw the MP, on my list to review :-)
[00:07] <nik90> ahayzen, btw how did you come to know about the trigger_leading_action() AP functions? Are there any docs on SDK helpers?
[00:07] <ahayzen> nik90, you talking of thomi reminded me, you ever seen his talk on Connascence ? https://www.youtube.com/watch?v=iwADIlIgDNA http://connascence.io/
[00:08] <nik90> ahayzen, I haven't...will check it out
[00:08] <ahayzen> nik90, https://developer.ubuntu.com/api/autopilot/python/1.5.0/ubuntuuitoolkit/#ubuntuuitoolkit.UCListItem.trigger_trailing_action
[00:08] <ahayzen> the SDK helpers from the docs :-)
[00:09] <nik90> cool thnx
[00:10] <ahayzen> AP is much easier now with all the helpers :-)
[00:54] <nik90> ahayzen, Do you happen to know how to use the SDK helpers for the new PageHeader? With UC 1.3 every page can potentially create its own PageHeader which is what we did with clock app. I am having trouble getting a reference to that PageHeader.
[00:54] <nik90> I have a class for say WorldCityPage(Page)
[00:54] <nik90> in that how do I grab its PageHeader?
[00:55] <nik90> I can no longer do self.main_view.get_header() because it is not mainview's header.
[00:55] <nik90> looking at autopilot3 vis, I only see "PageHeader" objects and not AppHeader which is referenced in the SDK Helper docs
[00:55] <ahayzen> i haven't tried it yet, still trying to get the PageHeader to act how i want :')
[00:56] <ahayzen> but i guess do a select_single of the header then apply as normal...but maybe not
[00:56] <ahayzen> hmmm
[00:56] <ahayzen> nik90, maybe talk to Tim, he may know if there are helpers
[00:56] <ahayzen> nik90, otherwise, put objectName's on things and then see if it can find them
[00:56] <nik90> will ask him tomorrow
[00:57] <nik90> well for now I did just used UCAbstractButton to click the header buttons
[00:57] <nik90> but I wanted to try the SDK helpers for this.
[00:57] <ahayzen> nik90, i'll be interested in the response, so could you relay to me if you find out :-)
[00:57] <ahayzen> ah cool
[00:57] <nik90> :)
[10:10] <nik90> JMulholland, ping
[10:44] <nik90> faenil, I tried cpulimit -l 1 qmlscene, however I am unable to link the c++ libraries that clock needs so it just fails there
[10:44] <faenil> nik90: more details
[10:44] <nik90> that said that listview has atmost 4 items..should it really slow down on a less performant hardware ;) ?
[10:45] <nik90> usually I run clock app as, qmlscene app/ubuntu-clock-app.qml -I builddir/backend/
[10:45] <nik90> however when I do cpulimit -l 1 qmlscene, it allow me to only choose the qml file and not the backend
[10:46] <faenil> if it's asking for the qml file then it means it's not receiving the parameters
[10:47] <nik90> I couldn't pass the qmlfile and backend as arguments in the cpulimit command.
[10:47] <nik90> it only allow passing the processid, path to executable etc.
[10:47] <nik90> I don't have a clock-app executable to run
[10:48] <faenil> nik90: are you sure the path to the qml is correct? it works fine here
[10:49] <faenil> nik90: otherwise, just try "cpulimit -l 1 -- <qmlblabla>"
[10:49] <nik90> ah you added "--"
[10:49]  * nik90 tried
[10:49]  * nik90 tries*
[10:50] <nik90> ok that works
[10:50] <faenil> :) good
[10:54] <faenil> nik90: more on the "--" here, if you're interested http://www.cyberciti.biz/faq/what-does-double-dash-mean-in-ssh-command/
[10:55] <nik90> faenil, With 1% CPU, the listitem expands, the height slowly increases to match the required height
[10:55] <nik90> Did you notice it failing to bind at 1% CPU?
[10:55] <faenil> nik90: I didn't test your branch, I just reviewed the code and suggested to check places where it could fail :)
[10:55] <nik90> as in never able to reproduce the scenario where the listview has loaded, but the height is not set to its requirements.
[10:56] <nik90> Ok, I will then comment on the MP
[10:56] <faenil> my worry was more about expansion.height changes not being reflected in the actualy ListItem logic, but it seems it's working as it should. I just wanted you to doublecheck ;)
[10:57] <faenil> instead of suggesting something that would have broken on phones :D
[10:57] <nik90> :)
[16:28] <balloons> popey, are you able to build the calendar app from the SDK?
[16:28] <popey> dunno, I am on 14.04 so the sdk is dead to me
[16:28] <balloons> I realize it is just qml, but opening the cmakelists file doesn't get me a project I can do anything with
[16:29] <popey> I only ever build using click-buddy
[16:56] <dholbach> jdstrand, popey just asked me to review com.ubuntu.clock_3.7.456_armhf.click and I'm seeing http://paste.ubuntu.com/15274605/
[16:56] <dholbach> popey, clock moved from multi to armhf?
[16:56] <popey> yes
[16:56] <dholbach> so that's intentional?
[16:56] <popey> yes
[16:57] <dholbach> ok
[16:57] <popey> Sorry, should I have warned someone? I apologise.
[16:57] <dholbach> jdstrand, can you maybe help popey with this review as I'm not quite sure how to respond
[16:57] <popey> Didn't think it would impact anything
[16:57] <dholbach> and I need to run in a few
[16:57] <dholbach> popey, so it was armhf+amd64 before?
[16:57] <popey> all 3
[16:57] <dholbach> (not sure if we have amd64 users of clock already)
[16:58] <popey> hmm
[16:58] <dholbach> jdstrand, the click-review explodes in the same way for the current version in the store as well
[16:59] <dholbach> all rightie... I need to run - see you all tomorrow!
[17:00] <dholbach> sorry popey for not being more helpful
[17:00] <popey> no prolemo!
[17:00] <popey> THanks!
[17:00] <dholbach> hugs!
[17:03] <nik90> balloons, hey, yes I can open calendar-app on 14.04 in qtc using cmakelist.txt
[17:07] <nik90> popey, can you push clock app to the store when're you free (added bonus of screenshots if possible)
[17:08] <popey> nik90: i have already, but it's failing click-review, dholbach asked jdstrand to look at it
[17:09] <nik90> balloons, I got a gift for you..fixed all clock app AP tests to PASS. Also added 3 stopwatch tests..and in the process of adding 3-4 settings tests.
[17:09] <nik90> popey, ah ok.
[17:09] <popey> \o/
[17:09] <balloons> nik90, you did? Awesome! Did you make a helper for the bottomedge?
[17:09] <balloons> nik90, are the new tests AP or qml?
[17:10] <nik90> balloons, no, I saw that bottomedge hint turned out in autopilot vis as a nice rectangle that you can swipe up, so it was easy to reuse code where possible.
[17:10] <nik90> balloons, AP
[17:11] <nik90> I was in the process of fixing the AP tests in trunk, when everything just clicked and went well..so added few additional tests
[17:11] <nik90> all feature tests
[17:11] <nik90> balloons, does jenkins run the clock-app AP tests?
[17:11] <balloons> gotcha.
[17:12] <balloons> nik90, see https://wiki.ubuntu.com/Touch/CoreApps/Jenkins#Workflow
[17:12] <balloons> rev. 3 or so. We're now working on running post merge, but on every merge
[17:13] <balloons> I think this may end up as the final state
[17:13] <nik90> hmm so it runs the AP test post-merge. Where do I see the test-results?
[17:14] <nik90> Does it post it in the MP still?
[17:14] <balloons> I haven't created the jobs yet. No it doesn't post to the MP the results of AP anymore. I've removed the AP job calls from all the ci jobs.
[17:14] <nik90> ok
[17:15] <balloons> if you need to see the results for your branch, we can just kick off a job
[17:15] <balloons> https://core-apps-jenkins.ubuntu.com/view/Release/job/release-build-test/
[17:15] <nik90> yup was just looking at it.
[17:15] <balloons> that will get you a build and AP test run you can look at
[17:16] <nik90> let me try it myself and see if I get it right
[17:16] <balloons> indeed, go for it
[17:18] <nik90> job #91 kicked off..
[17:23] <nik90> balloons, hmm #91 didnt run AP tests..do I have to explicitly ensure that the job name ends with "run-ap-tests-*" to ensure it runs AP?
[17:23] <nik90> it commented in the MP as expected.
[17:33] <balloons> nik90, what do you mean?
[17:33] <balloons> this? https://core-apps-jenkins.ubuntu.com/job/clock-app-ci/91/
[17:33] <balloons> yes, notice the downstream projects doesn't include the run-ap-tests job anymore :-)
[17:33] <balloons> build with this: https://core-apps-jenkins.ubuntu.com/view/Release/job/release-build-test/
[17:34] <balloons> it's generic for any branch
[17:34] <balloons> it won't leave a comment on the mp, and you'll have to view the job yourself
[17:37] <balloons> nik90, so it's running now: https://core-apps-jenkins.ubuntu.com/view/Release/job/run-ap-tests-release/7/console
[17:37] <nik90> balloons, erm I started #5 for that
[17:38] <balloons> it is your run.. I didn't start it
[17:38] <nik90> balloons, that said, how do I get to the release-build-test page from core-app-jenkins.com?
[17:38] <balloons> https://core-apps-jenkins.ubuntu.com/view/Release/
[17:39] <balloons> I guess we can point anyone at the job, unless you'd like something else to build your branches more easily
[17:40] <balloons> the only annoying bit is having to have two jobs to do a run, because we can't build the clicks on the device
[17:40] <nik90> from https://core-apps-jenkins.ubuntu.com/view/Release/ what do I click? I tried the sidebar links like "New Item"
[17:41] <balloons> nik90, ohh.. You click release-build-test, then 'build with parameters'
[17:41] <nik90> ah found it
[17:41] <nik90> thnx
[17:42] <balloons> sounds like building this is not as easy as I thought
[17:42] <balloons> so feel free to give comments on what you'd like to see and we can discuss, then document
[17:44] <balloons> nik90, if you want to re-test now, assuming you don't change the app itself, you can simply rebuild https://core-apps-jenkins.ubuntu.com/view/Release/job/run-ap-tests-release/7/
[17:44] <balloons> does that make sense?
[17:44] <balloons> aka, commit changes, push them to your branch, re-run
[17:44] <nik90> yup makes sense
[17:45] <nik90> already notice it failing on krillin...bah :/
[18:00] <nik90> balloons, just checkout the autopilot.subunit file with trv, 5 out of 8 tests are failing. The alarm tests are failing because the keyboard doesn't popup. Surely that's a system-bug?
[18:01] <balloons> nik90, it is
[18:01] <balloons> i don't know the bug offhand sadly
[18:01] <balloons> but it
[18:01] <balloons> it's filed
[18:01] <nik90> it says KeyboardContainer.activeKeypadState failed:'Shifted' != dbus.String('Normal', variant_level=1)
[18:01] <nik90> ok
[18:02] <nik90> balloons, well the tests pass locally for me...no flaky ones.
[18:02] <nik90> so I'm happy with that.
[18:02] <nik90> I will run my own AP tests when I review other people's branches to ensure this doesn't fail.
[18:11] <Guest99940> hi. first attempt to create a scope by following the tutorial. when i run it I get an error saying "This application failed to start because it could not find or load the Qt platform plugin "xcb".  Reinstalling the application may fix this problem. The program has unexpectedly finished. /usr/ubuntu-sdk-ide/share/qtcreator/ubuntu/scripts/qtc_desktop_scoperunner.py crashed"
[18:12] <Guest99940> how do i add xcb?
[18:15] <Guest99940> sudo apt-get install xcb says it is already installed
[18:19] <dobey> Guest99940: running it with unity-scope-tool?
[18:20] <Guest99940> hmm, not sure. i clcked the green play button in qt creator
[18:21] <Guest99940> i am totally new to this so i may be missing something very obvious.
[18:28] <Guest99940> @dobey no i am not running unity-scope-tool.
[18:29] <Guest99940> its working now.
[18:30] <dobey> ok
[18:30] <Guest99940> i dont know if it was connected but a software update 7MB was waiting. updated it. restarted qt creator. it works
[18:30] <Guest99940> not sure what i did though. anyway. thanks.
[19:28] <peter-bittner> I'm having trouble identifying the correct policy_groups for my webapp. It should allow WebRTC in oxide, so audio and video (i.e. camera access).
[19:33] <peter-bittner> According to [1] it should be "camera", but `click-review` complains.
[19:33] <peter-bittner> [1] https://developer.ubuntu.com/en/start/platform/guides/app-confinement/#Usage-1
[21:04] <jdstrand> popey: fyi, com.ubuntu.clock_3.7.456_armhf.click review looks fine
[21:05] <jdstrand> popey: as in no tracebacks
[21:05] <popey> hm
[21:05] <popey> locally?
[21:05] <jdstrand> popey: both review tools 0.38 and trunk are working correctly. I think maybe the store was in a bad spot-- it just got updated a few hours ago
[21:06] <popey> jdstrand: would you mind reviewing it in the store so I can publish it please?
[21:06] <jdstrand> popey: yes, locally, but the store looks fine too: https://myapps.developer.ubuntu.com/dev/click-apps/121/rev/37/
[21:06] <popey> ah i see
[21:07] <jdstrand> popey: has this always used the calendar?
[21:09] <jdstrand> it looks like it
[21:09]  * jdstrand approves
[21:11] <popey> yes
[21:11] <popey> thanks
[21:11] <peter-bittner> I'm having problems with policy_groups with a web app I'm trying to submit. I can't take the click-review on my local machine as a reference, because it complained on version 0.1 of my package while this passed the review online.
[21:13] <nik90> ahayzen, did you by chance happen to move the Slider{} in your music=app AP tests?
[21:13] <ahayzen> nik90, hmm, we definitely used to
[21:13] <ahayzen> just a simple calc on the width then click at that x,y
[21:13] <peter-bittner> I need additional policy_groups for the web app in order to allow access to the camera and microphone. I added that according to [1], but unfortunately the review failed after submission of version 0.2 [2].
[21:14] <peter-bittner> [1] https://developer.ubuntu.com/en/start/platform/guides/app-confinement/#Usage-1
[21:14] <peter-bittner> [2] https://myapps.developer.ubuntu.com/dev/click-apps/4646/rev/2/
[21:14] <ahayzen> but now IIRC we just do something like .position.wait_for(5000) or something
[21:14] <ahayzen> however i think we even managed to remove those
[21:14] <nik90> ahayzen, yup makes sense
[21:14] <ahayzen> nik90, but doing a click is pretty simple if that is what you need
[21:15] <peter-bittner> The failing review points are:
[21:15] <peter-bittner> "found unusual policy groups: connectivity, camera, microphone security_policy_groups_webapp (appear-in.apparmor)"
[21:15] <ahayzen> just get the vertical centre, and then calc the x position
[21:15] <nik90> ahayzen, well even I do the click, I wouldn't be to verify that the alarm volume is a certain value.
[21:16] <nik90> maybe this is a better candidate for QML tests
[21:16] <ahayzen> nik90, you'd be able to verify the slider was correct...and the backend that that is setting is of the correct value
[21:16] <ahayzen> yeah, i was about to say that ;-)
[21:16] <nik90> ;)
[21:18] <popey> nik90: clock published
[21:19] <nik90> popey, woohoo..thnx
[21:19] <popey> Ooh! Need new screenshots!
[21:19] <nik90> wow clock only 456 kb...
[21:20] <popey> thats the bzr rev :)
[21:21] <popey> spooky
[21:21] <nik90> haha
[21:53] <peter-bittner> Anyone know more about the policy_groups? The latest policy_version is 1.3, correct?
[21:53] <nik90> peter-bittner, yes 1.3 is latest
[21:54] <peter-bittner> And the policy_groups listed on [1] are the ones matching version 1.3?
[21:54] <peter-bittner> [1] https://developer.ubuntu.com/en/start/platform/guides/app-confinement/#Usage-1
[21:57] <peter-bittner> If yes, why is the review of my app failing with "found unusual policy groups: connectivity, camera, microphone security_policy_groups_webapp (appear-in.apparmor)"?
[21:59] <nik90> peter-bittner, I am not familiar with the last policy group (webapp) since I only work on native apps.
[21:59] <nik90> Perhaps it is best to look at an existing web-app to see how they do things
[22:00] <nik90> search https://uappexplorer.com/ for good webapps and look at their source code. Most are open-source
[22:00] <peter-bittner> I have a bunch of web apps, but it's the first time I need to access camera and microphone (because oxide didn't support it half a year ago).
[22:03] <peter-bittner> Can't wait to be told this is a restriction of web apps. As designed in 2014.  *nirg*  :-/
[22:05] <jdstrand> peter-bittner: please submit it. it will trigger a manual review and I'll get pinged. I'll talk to the oxide devs about it. they are offline now
[22:06] <peter-bittner> Done. It's submitted. https://myapps.developer.ubuntu.com/dev/click-apps/4646/rev/2/
[22:07] <peter-bittner> jdstrand: Do you have access to my app review / submission=
[22:07] <peter-bittner> ?
[22:07] <jdstrand> yes
[22:08] <jdstrand> I've added it to me todo to talk to them tomorrow
[22:08] <peter-bittner> It was "automatically rejected".
[22:08] <peter-bittner> Thank you.
[22:08] <jdstrand> peter-bittner: can you click the 'request manual review' button?
[22:09] <peter-bittner> Done. Now the red button is gone.
[22:10] <peter-bittner> jdstrand. Do you happen to know whether it's possible to control which camera is used by the web app (by default)?
[22:10] <jdstrand> peter-bittner: I don't. oSoMoN might
[22:11] <jdstrand> he is one of the people that are eod that I was going to talk to though
[22:11] <peter-bittner> oSoMoN = ?
[22:11] <peter-bittner> Ah, okay.
[22:12] <peter-bittner> I'm asking because in the web app there will be no way to access the browser settings menu. Only there you can switch between the rear and the front camera.