[01:43] <beuno_> gcollura, hey
[01:43] <beuno_> it doesn't affect existing apps at all
[02:41] <ahoneybun> anyone still online to help out with a twitter scope?
[07:27] <nik90_> zsombi: ping
[07:27] <nik90_> Good Morning
[07:27] <zsombi> nik90_: good :)
[07:28] <nik90_> zsombi: hey, I noticed a different behaviour in the listitem in rtm and in vivid currently which is causing my clock app qml tests to fail. (I am not referring to the new listitems)
[07:28] <zsombi> nik90_: that's weird, because all changes in RTM are also synched to vivid
[07:29] <nik90_> I am using a ListItem.Standard + Control (Switch) where in rtm, the user can click anywhere in the listitem to enable/disable the switch. While in vivid, they have to explicitly click the switch to enable/disable it.
[07:29] <zsombi> nik90_: aaah, yers
[07:29] <nik90_> and my qml tests click in the middle of the listitem and thereby work on rtm as expected but fail in jenkins since it runs vivid
[07:29] <zsombi> nik90_: that behavior is a bug in RTM
[07:29] <nik90_> really?
[07:29] <zsombi> nik90_: yes
[07:30] <nik90_> It seems a bit of a inconvenience to press on the tiny switch box explictily to enable it
[07:30] <zsombi> nik90_: I'll try to find the bug
[07:31] <zsombi> nik90_: well, it is also inconvenient to alter a state of a component if you tap anywhere on teh item :)
[07:31] <nik90_> :P
[07:31] <zsombi> nik90_: and teh checkbox is big enough to aim it ;)
[07:31] <nik90_> zsombi: well it was made smaller in vivid
[07:31] <zsombi> nik90_: the new ListItem behaves teh same
[07:31] <nik90_> anyway I will adapt my qml tests to the new behaviour
[07:31] <zsombi> nik90_: yes, but not much smaller :P
[07:32] <zsombi> nik90_: however, with the new ListItem you can have that behavior, simpli toggle teh state of teh CheckBox in onClicked, and saionara
[07:33] <zsombi> nik90_: I'm really curious to see your feedback on the new ListItem API....
[07:33] <nik90_> hmm that's true
[07:33] <nik90_> zsombi: oh I checked out the demo of the new listitem in the sdk gallery. I will check out the API today with some sample apps to get a feel for them
[07:33] <zsombi> nik90_: the current staging does not contain teh whole API yet, i.e. select and drag modes are not there, pressAndHold is also missing, etc
[07:33] <nik90_> yeah I am keeping track of your branches
[07:34] <zsombi> nik90_: you can have as many actions as you want in both leading and trailing side
[07:34] <zsombi> nik90_: you can show them each differently
[07:34] <nik90_> so I just import Ubuntu.Components 1.2 with the ubuntu-14.10 framework to get the new listitems?
[07:34] <zsombi> nik90_: more, you can define your own style to trigger the actions!
[07:34] <nik90_> cool
[07:35] <zsombi> nik90_: unfortunately it is not enough... you need to use ListItem from Ubuntu.Components
[07:35] <nik90_> ok
[07:35] <zsombi> nik90_: I am still trying to find out whether we could put that as base for teh old ListItems, for a sake of transitions, but that might not be possible as I might not be able to support all the API there
[07:36] <zsombi> nik90_: and we still need the layouts, this ListItem is an empty dude, does nothing
[07:36] <zsombi> nik90_: with teh layout I mean :D
[07:37] <nik90_> ack,
[07:37] <zsombi> nik90_: and yes, one more thing: the current style implementation of the leading/trailing actions triggers teh action when the snap out animation completes
[07:37] <zsombi> nik90_: the deletion must be handled by you guys
[07:37] <zsombi> nik90_: as well as teh animation
[07:38] <zsombi> nik90_: but, tbh, the current ListItem's doing teh delete animation is a bad practice
[07:38] <nik90_> oh
[07:38] <zsombi> nik90_: ListView has removeDisplaced transition, that should be used!
[07:38] <nik90_> true
[07:39] <nik90_> that should be ok..although now that I think about it, the delete animation was never explicitly mentioned by the designers
[07:39] <zsombi> nik90_: and, UbuntuListView will have the moveDisplaced animation set by default, so when you drag, that will be doing the animation for you
[07:40] <zsombi> nik90_: no more need for DelegateGroups to track selected items
[07:40] <zsombi> nik90_: ListView.ViewItems.selectedIndexes (the name might change) will have the indices selected
[07:40] <nik90_> oh yeah the new listitems provides multiselect mode ... sweet!
[07:41] <nik90_> I have a separate clock vivid branch where I can try these new experimental listitems and remove our custom implementations of it.
[07:41] <zsombi> nik90_: dragging is on your hands, you get ListView.ViewItems.onDraggingStarted() and onDraggingUpdated() signals, where the first one can be use to pose restrictions on the dragging  and the second one is mandarory to implement and you will there decide when to move teh model
[07:42] <zsombi> nik90_: like in start signal you can restrict moving elements out of a section for instance
[07:42] <zsombi> nik90_: or lock teh first n items in a ListView from being dragged at all
[07:42] <nik90_> ah ok
[07:43] <zsombi> nik90_: I hoipe you guys are gonna like it :)
[07:44] <nik90_> zsombi: well it is getting a ton of features..what's not to like in them :P
[07:44] <nik90_> s/getting/got
[07:45] <zsombi> nik90_: :D
[07:45] <zsombi> you never know...
[07:46] <nik90_> :)
[07:54] <nik90_> popey: Here is the MP https://code.launchpad.net/~nik90/ubuntu-clock-app/update-alarm-page-ui-correctly/+merge/246657 that fixes the alarm page ui refresh as promised in the meeting yesterday.
[07:56] <dholbach> good morning
[07:58] <nik90_> dholbach: good morning :)
[07:58] <nik90_> and also Happy B'day!!!!!!!!!!!!!!
[08:03] <dholbach> thanks nik90_ - and good morning to you too
[08:10] <AkivaAvraham> morning
[08:31] <justCarakas> morning
[08:44] <popey> thanks nik90
[09:20] <nik90> popey: mind kicking jenkins on https://code.launchpad.net/~nik90/ubuntu-clock-app/update-alarm-page-ui-correctly/+merge/246657
[09:20] <popey> sure
[09:20] <nik90> thnx
[09:20] <popey> running...
[09:37] <nik90> popey: hey, who in the QA team familiar with autopilot is online at this time? I would generally ask balloons, but I would presume he's not online yet
[09:37] <popey> nik90: brendand
[09:37] <nik90> popey: cool, thnx
[09:38] <nik90> brendand: ping
[09:39] <brendand> nik90, hey
[09:39] <AkivaAvraham> nik90, did you see my new autopilot plugin?
[09:39] <nik90> brendand: hey, I am getting a AP failure on jenkins that I am unable to resolve. http://91.189.93.70:8080/job/generic-mediumtests-vivid/698/?
[09:39] <nik90> brendand: the video log doesnt seem to open for me either
[09:40] <nik90> AkivaAvraham: erm no I didnt...got a link?
[09:40] <AkivaAvraham> https://www.youtube.com/watch?v=gTNWyXj94HE&feature=share
[09:40] <AkivaAvraham> nik90, wip; working on getting autopilot to be autodetected,
[09:40] <popey> nik90: he's on a video call right now.
[09:40] <nik90> popey: ack.
[09:41] <AkivaAvraham> and something else... in any case; its working right now, and it allows you to run autopilot from the sdk.
[09:41] <nik90> AkivaAvraham: Is this something we could see merged into qtcreator-plugin-ubuntu in the future?
[09:41] <AkivaAvraham> nik90, yes, if I can satisfy the two requirements layed out by bzoltan_
[09:42] <AkivaAvraham> auto detection and... what was it...
[09:42] <AkivaAvraham> oh and running on devices
[09:42] <AkivaAvraham> https://code.launchpad.net/~akiva/qtcreator-plugin-autopilot/trunk
[09:44]  * nik90 watches the video
[09:46] <JamesTait> Good morning all; happy Friday, and happy International Hot and Spicy Foods Day! :-D
[09:47] <AkivaAvraham> JamesTait, If you are anything, you are predictable and reliable.
[09:47] <AkivaAvraham> You never miss a beat in your greetings.
[09:48] <JamesTait> AkivaAvraham, I'm reading "You should have gone for Nothing Day". ;)
[09:48] <AkivaAvraham> o_o
[09:48] <AkivaAvraham> :)
[09:51] <nik90> AkivaAvraham: the plugin look pretty cool. Nice work!
[09:54] <AkivaAvraham> nik90, thanks. Now I just need to become better versed in c++ classes, namely how to gain access to qtcreator's currently opened projects.
[09:55] <nik90> it would be nice to add a new button to the left sidebar where in that tab, devs can see the list of tests, test logs and other stuff
[09:55] <AkivaAvraham> nik90, yah I was thinking that too.
[09:56] <brendand> nik90, the videos do seem to be broken
[09:56] <brendand> nik90, you'd need someone with jenkins expertise to see why they can't be downloaded
[09:56] <AkivaAvraham> nik90, as it stands, the latest version will check mark the test you ran, and seems to work well as is.
[09:56] <nik90> brendand: yeah...so I tried running the tests locally, but the repeating alarms tests fail for me ... let me paste the output
[09:57]  * nik90 brendand: just the last few lines of ap fail log -> http://paste.ubuntu.com/9760705/
[09:57] <nik90> brendand: and I am pretty sure that this has nothing to do with my MP.. I will try with trunk just to confirm that
[09:58] <brendand> nik90, locally on desktop or mako?
[09:58] <nik90> brendand: locally on desktop
[09:59] <nik90> the clock app starts with the a white screen and then immediately ends
[09:59] <bzoltan_> nik90: I am in :) but this test importing feature should be integrated to the active open project. So we should not have a separate "open" path ... I open a project and I want to see the tests on a Tests tab. And when I say "Run tests" then the tests are executed on the device what is assigned to the selected Kit. So it all comes together to the same flow.
[10:00] <nik90> brendand: I think something is wrong with my test environment
[10:01] <nik90> bzoltan_: cool.. makes sense
[10:06] <mzanetti> popey: rpadovani: http://notyetthere.org/data/com.ubuntu.developer.mzanetti.machines-vs-machines_0.1.2_armhf.click
[10:06] <popey> hah, haven't had time to play with the last one yet!
[10:06] <popey> :)
[10:39] <sturmflut-work> I intend to build a cheap Network Scanner app, but QtNetwork doesn't support ICMP. Are there any other approaches besides calling /"bin/ping" using QProcess and parsing its output?
[10:51] <AkivaAvraham> Finally!  Okay remember; reference error is a dependency issue in .pro >:S
[10:52] <mivoligo> mzanetti: ping
[10:52] <AkivaAvraham> pang
[10:52] <mivoligo> :)
[10:52] <AkivaAvraham> ;)
[10:55] <mivoligo> Any native English speaker please help. Is it a proper sentence: „You have collected all the stars playing at easy difficulty”?
[10:55] <AkivaAvraham> mivoligo, mmmm its decent, but a bit fandangled.
[10:55] <AkivaAvraham> First of all, ",," is incorrect.
[10:55] <AkivaAvraham> ;)
[10:55] <mzanetti> mivoligo: hey ho
[10:56] <mivoligo> mzanetti: hey
[10:56] <mivoligo> mzanetti: I'd like to show you my first end of the game proposition
[10:57]  * mzanetti leaves the native english speakers precedence
[10:57] <mivoligo> AkivaAvraham: what are the other problems
[10:57] <AkivaAvraham> "You have collected every star on "Easy Difficulty" " is one way perhaps
[10:57] <AkivaAvraham> mivoligo, -at +on
[10:58] <AkivaAvraham> -all the stars +each star || +every star  -- if you want it to be shorter.
[10:58] <mzanetti> shouldn't we perhaps use "easy mode" instead of "easy difficulty"
[10:58] <AkivaAvraham> ^
[10:58]  * mzanetti finds difficulty a strange word for some reason :D
[10:58] <mivoligo> AkivaAvraham: does not need to be very short
[10:59] <mivoligo> mzanetti: ok
[11:00] <mzanetti> AkivaAvraham: here you'll get an updated package for your help: mivoligo: ah great. I've enabled full screen mode
[11:00] <mzanetti> :D
[11:00] <mzanetti> sorry. wrong paste :D
[11:00] <AkivaAvraham> I would almost be tempted to take out "On easy mode" or "On easy difficulty", but rather make it an achievement.
[11:00] <mzanetti> http://notyetthere.org/data/com.ubuntu.developer.mzanetti.machines-vs-machines_0.1.2_armhf.click
[11:00] <AkivaAvraham> so
[11:01] <AkivaAvraham> Achievement: Easy Mode - "Collected every star!"
[11:01] <AkivaAvraham> mivoligo, in any case, you can go with your original, just replace "at" with "on"
[11:01] <mivoligo> AkivaAvraham: I'd prefer it to be a sentence
[11:02] <AkivaAvraham> "at" implies a location.
[11:02] <AkivaAvraham> "Easy Difficulty" is not a location.
[11:02] <justCarakas> mzanetti maybe also include something to force it in landscape because portait is too small on the phone, buttens overlap
[11:02] <AkivaAvraham> blah blah blah - oh btw!  Do you have any screenshots?
[11:02] <mivoligo> AkivaAvraham: „you have collected every star playing on easy mode” is that good?
[11:02] <justCarakas> also a mute button would be nice
[11:03] <AkivaAvraham> Why are the quotes on the bottom?
[11:03] <justCarakas> now I can't play it at work during my break because there are always sounds coming trough even togh I set my volume to 0
[11:03] <mivoligo> AkivaAvraham: there won't be any quotes
[11:04] <AkivaAvraham> mivoligo, yep its fine!
[11:04] <mivoligo> AkivaAvraham: great, thanks :) „„„„„„„„„ „„„„ :D
[11:04] <mzanetti> justCarakas: can't force it to landscape atm
[11:04] <AkivaAvraham> ,,,,,,,,,,,,,,,,,,
[11:04] <mzanetti> justCarakas: not supported, or am I missing something?
[11:05] <mzanetti> justCarakas: there are sound settings
[11:07] <mivoligo> mzanetti: see finish-easy in the drive
[11:08] <mzanetti> mivoligo: nice :) I like the popcorn bag with stars
[11:09] <mzanetti> mivoligo: could the well-done banner have some fewer corners? :D
[11:09] <mivoligo> ?
[11:10] <mivoligo> mzanetti: no ribbon effect, you mean
[11:11] <mzanetti> ribbon effect?
[11:11] <mzanetti> I mean more like this: http://www.vectorfree.com/media/vectors/fancy-banner-vectors.jpg
[11:12] <mivoligo> mzanetti: ak, you like it to be more round
[11:12] <mzanetti> mivoligo: having some broken enemies and parts from the explosion effect laying around would be cool
[11:12] <mivoligo> mzanetti: yes, but for easy mode, just a popcorn :D
[11:15] <mzanetti> ah ok :D
[11:15] <mzanetti> mivoligo: cool :)
[11:17] <mivoligo> mzanetti: from a technical point of view I think to make its width and height same as level backgrounds, so we can adjust it in the same way to the screen. What do you think?
[11:18] <mzanetti> mivoligo: +1
[11:28] <AkivaAvraham> nik90, ping  - do you know if there is a mandatory filename for autopilot? I am trying to catch whether a project has an autopilot suite in it.
[11:28] <AkivaAvraham> popey, ^ same question to you.
[11:29] <popey> ← Not an autopilot expert.
[11:29] <popey> ^ brendand
[11:29] <AkivaAvraham> ty
[11:30] <brendand> AkivaAvraham, the convention is to have a directory called autopilot, but it is not technically necessary
[11:30] <AkivaAvraham> brendand, what about an __init__.py?
[11:31] <brendand> AkivaAvraham, but it is necessary to derive your test classes from 'AutopilotTestCase' so you could grep for that
[11:31] <AkivaAvraham> mmmm wish I had more than a convention.
[11:32] <brendand> AkivaAvraham, __init__.py is a python thing not autopilot
[11:32] <AkivaAvraham> brendand, Yah I know. my goof.
[11:33] <AkivaAvraham> hmmmm okay ; is that AutopilotTestCase going to be in a .py file?
[11:33] <mivoligo> mzanetti: take a look at the second version in the drive
[11:33] <justCarakas> mzanetti: I have seen apps where you get an animation telling you to turn the device if it is in landscape, maybe you can try something like that ?
[11:33] <mivoligo> mzanetti: I'd like to keep it rather simple for the easy mode :)
[11:34] <mzanetti> justCarakas: hmm... there should be.
[11:34] <mzanetti> justCarakas: which version do you have?
[11:34] <mzanetti> the info dialog just says 0.1, check the click package's version you installed
[11:35] <mzanetti> 0.1.1 doesn't have it, 0.1.2 should have it
[11:35] <mzanetti> mivoligo: better, but it's still a bit straight imo
[11:35] <mivoligo> mzanetti: ok ok :)
[11:35] <mzanetti> mivoligo: the banner gives the impression that it's made of fabric, yet it's totally straight like some solid material
[11:35] <mzanetti> know what I mean?
[11:36] <mivoligo> I know :)
[11:39] <AkivaAvraham> okay .py files it is :)
[11:43] <AkivaAvraham> ah I guess not all projects have the python tests included in their projects.
[11:43] <AkivaAvraham> brendand, good suggestion on the grep
[11:45] <mivoligo> mzanetti: check the version 3
[11:46] <mzanetti> mivoligo: now we're talking :)
[11:46] <mivoligo> :D
[11:46] <mzanetti> mivoligo: I also have a nice outro music :D
[11:46] <mivoligo> mzanetti: great!
[12:00] <joe> how do we import the example in qtcreator
[12:58] <justCarakas> mzanetti: I had 0.1 I now installed 0.1.2 but that one wont start
[12:58] <justCarakas> nexus 4
[13:01] <mzanetti> strange
[13:01] <mzanetti> justCarakas: you sure you refreshed the home screen?
[13:01] <mzanetti> or rebooted?
[13:02] <justCarakas> I havent rebooted
[13:02] <justCarakas> Ill try that later
[13:02] <mzanetti> if the app version changes, the apps scope won't pick it up
[13:02] <justCarakas> ok :)
[13:02] <mzanetti> pull it down to refresh it, it should work
[13:02] <mzanetti> alecu_: ^ :)
[13:03] <justCarakas> thx that worked
[13:16] <alecu_> justCarakas: did you install the click from the cmdline, or from the store?
[14:14] <justCarakas> cmdline
[14:43] <om26er> artmello, Hi! can you tell if gallery is a click package ?
[14:44] <artmello> om26er: yes, it is
[14:45] <om26er> artmello, oh, ok. I found the click package in the sheet.
[14:51] <om26er> artmello, how do I install the click with right permissions ?
[14:52] <artmello> pkcon install-local com.ubuntu.gallery<version>.click --allow-untrusted
[14:54] <dpm> mzanetti, rpadovani, I had a chat with Penk and cwayne last night. It seems Penk is no longer working on the scope. What I've done is to grab the code from the private branch and put it in a reminders-app branch, so that we can merge it from there
[14:54] <dpm> I've just rearrange the layout, so it does not even build yet, but I'll see if I can get it to build and include it in the click package this weekend
[14:54] <dpm> https://code.launchpad.net/~dpm/reminders-app/scope
[15:02] <mzanetti> dpm: this doesn't look right: http://bazaar.launchpad.net/~dpm/reminders-app/scope/files/head:/src/scope/data/
[15:03] <mzanetti> dpm: also it doesn't use the libqevernote yet (and with it no cache or offline mode)
[15:03] <elopio> kenvandine: it seems the job for system settings is broken at some point in the lab.
[15:03] <mzanetti> dpm: might be a nice task for rpadovani once he's done with exams. let's see if he's willing to pick it up.
[15:03] <dpm> mzanetti, there seems to be 2 .ini files too much you mean? As I said, I just copied over the code and rearranged the layout to have it in a reminders-app branch
[15:03] <kenvandine> elopio, yeah, i asked for cihelp
[15:04] <elopio> kenvandine: I was told last week that somebody from ci was going to fix it. But it seems you will need to poke the vanguard again.
[15:04] <kenvandine> elopio, the tests pass though :)
[15:04] <kenvandine> elopio, i poked them an hour ago
[15:04] <elopio> kenvandine: ok, you are two steps ahead.  I'll just shut up :)
[15:04] <kenvandine> elopio, don't do that :)
[15:04] <kenvandine> elopio, i wanted to ask you about a similar question to what we talked about yesterday
[15:05] <mzanetti> dpm: yeah... looks like there are generated files comitted.. but yeah, I guess this needs to be reworked quite a lot
[15:05] <kenvandine> to get the about page tests to pass in rtm, i had to make a change to the page validation stuff
[15:05] <kenvandine> ItemPage vs. PageComponent
[15:05] <kenvandine> one works in vivid
[15:05] <kenvandine> and the other works in rtm
[15:06] <elopio> kenvandine: do you have different branches for vivid and rtm?
[15:06] <kenvandine> elopio, yes, we have quite a delta too
[15:06] <kenvandine> elopio, hoping to sync after the 30th
[15:06] <kenvandine> http://bazaar.launchpad.net/~ken-vandine/ubuntu-system-settings/rtm-less_flaky/revision/960
[15:07] <kenvandine> elopio, i had to do that to get tests to pass on rtm
[15:07] <kenvandine> but the same change breaks tests on vivid...
[15:07] <kenvandine> elopio, any insight?
[15:07] <elopio> kenvandine: you could do a trick, like putting on the validate_dbus_object:
[15:07] <elopio> if name == 'PageComponent' or name == 'ItemPage':
[15:07] <elopio>     return True.
[15:08] <kenvandine> that would help for sync, but i'm more concerned about why...
[15:08] <kenvandine> perhaps something else in the sdk that differs?
[15:08] <elopio> kenvandine: but this generally means that your QMLs are different between the two versions. If you have different versions, the versions of the tests should be different too. That's lot saner than making a test that adapts to all the possible versions.
[15:09] <elopio> kenvandine: we would have to check the code. But it's like this:
[15:09] <elopio> when you have a qml file that extends from PageComponent, qt reports it to autopilot as being named 'PageComponent'
[15:09] <kenvandine> i'd be surprised if that differs between rtm and vivid
[15:09] <elopio> once you add a property to that qml file, qt no longer considers it a PageComponent, it reports it to autopilot as being named just like the qml file.
[15:10] <kenvandine> i'll double check
[15:10] <elopio> kenvandine: one second to give you a link...
[15:10] <kenvandine> thx
[15:11] <elopio> kenvandine: http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/revision/1228#plugins/about/PageComponent.qml
[15:11] <elopio> kenvandine: when jgdx added that modemsSorted property, he changed the type we see in the qml tree.
[15:12] <elopio> it's a little crazy what we can introspect out of the running app. That's why we added the validate_dbus method.
[15:13] <kenvandine> elopio, oh... so just adding that property do a PageComponent did that?
[15:13] <elopio> kenvandine: yes. If you just inherit using the existing properties, it will be named as the parent.
[15:13] <elopio> if you extend adding new properties, it will be named as your qml file.
[15:14] <kenvandine> wait... in trunk it matches PageComponent
[15:14] <kenvandine> in rtm it matches ItemPage
[15:14] <kenvandine> oh
[15:14] <kenvandine> nm
[15:14] <kenvandine> i see your point :)
[15:14] <kenvandine> i thought this fix landed in rtm though... i'll double check that backport
[15:15] <elopio> kenvandine: generally, it will be because you didn't land the same things in the two branches. So my recomendation is to keep the tests different as you are keeping the QMLs different.
[15:15] <elopio> sometimes, it will be harder.
[15:15] <elopio> like the change comes from the SDK, or from an even deeper dependency.
[15:15] <kenvandine> elopio, indeed
[15:15] <elopio> in that case, we can use tricks to keep the tests working with the same code for two versions.
[15:20] <kenvandine> elopio, i see, that wasn't backported yet
[15:20] <kenvandine> man i hate having this delta!
[15:23] <elopio> kenvandine: tell me about that! we have to automate a sanity suite that works on rtm and vivid, so if we have a test that uses unity, an indicator and an app, sometimes we find that the versions for the three are different.
[15:26] <kenvandine> elopio, ugh... no fun
[16:09] <daker> aquarius: official response https://bugs.launchpad.net/ubuntu-html5-theme/+bug/1338445/comments/6
[16:09] <aquarius> daker, ah, ok
[16:10] <aquarius> I shall comment
[16:10] <daker> aquarius: if you want :)
[16:10] <aquarius> done so, just so the app.js gets fixed :)
[16:18] <rpadovani> mzanetti, dpm I'll take a look :-)
[16:25] <AkivaAvraham> brendand, mmmm I found an autopilot test that does not have AutopilotTestCase in it :/
[16:25] <brendand> AkivaAvraham, do tell
[16:25] <AkivaAvraham> brendand, its in one of the templates. I have an untitled project here.... nothing. Let me double check though.
[16:36] <AkivaAvraham> brendand, confirmed. I picked the first template, and created a new project
[16:36] <AkivaAvraham> brendand, the template had two tests, and not once did they have the term AutopilotTestCase
[16:36] <AkivaAvraham> brendand, do you know if there is a neccessarry import perhaps?
[16:37] <brendand> AkivaAvraham, can you pastebin the files?
[16:37] <AkivaAvraham> brendand, do you want my grep output, or the test files?
[16:37] <brendand> AkivaAvraham, the files
[16:37] <AkivaAvraham> sure
[16:40] <AkivaAvraham> brendand, http://pastebin.ubuntu.com/9762434/
[16:40] <AkivaAvraham> both files are in one pb
[16:43] <mhall119> dpm: latest devportal code is in production
[16:44] <mhall119> I've setup the blog in chinese, and added one article to it for now: https://developer.ubuntu.com/zh-cn/community/blog/
[16:44] <mhall119> I've also set every other article to the English category so it they show up properly
[16:45] <AkivaAvraham> brendand, bb in 30 minutes.
[16:48] <doflaherty> how well supported are svg images in scopes?  I'm trying out a clippath but it doesn't actually clip and shows the whole image
[16:50] <dpm> awesome, thanks mhall119
[16:53] <dpm> mhall119, could you set up the "Keep up-to-date" section on the front d.u.c page to show only the Chinese blog posts? For the "Keep up-to-date", "Latest from the blog" and "Latest events" texts, you can use the English text, and I'll update it with the Chinese translation
[17:09] <AkivaAvraham> brendand, so whats the deal with the tests?
[17:09] <brendand> AkivaAvraham, yeah, see they derive from UbuntuUIToolkitAppTestCase
[17:10] <brendand> AkivaAvraham, you could grep for autopilot (lowercase) as well
[17:10] <brendand> AkivaAvraham, but it is possible to write a valid set of autopilot tests without mentioning the word autopilot anywhere in your code
[17:10] <AkivaAvraham> brendand, I'm afraid of having multiple results.
[17:11] <AkivaAvraham> lol blast
[17:11] <balloons> lol
[17:11] <mhall119> dpm: done, but the latest articles on the chinese page is still showing everything, I suspect it's cached it from before I added the filtering
[17:12] <AkivaAvraham> I could brute force "autopilot list [folder name]" recursively I suppose... See any issue with that?
[17:12] <AkivaAvraham> brendand, ^
[17:13] <nik90> balloons: ping
[17:14] <dpm> mhall119, I had some issues with the filtering when I added the section on the English page. I wasn't sure if it was the caching or a bug in the filters
[17:14] <balloons> nik90, pong! How is 2015 for you? :)
[17:14] <brendand> AkivaAvraham, it's a long story
[17:14] <nik90> balloons: hey, 2015 seems ok..started of a bit busy :) How about you?
[17:14] <balloons> nik90, eventful for me as well, but much better now
[17:15] <nik90> balloons: wait you injured your arm, how is it now?
[17:15] <nik90> iirc
[17:15] <balloons> nik90, yes my wrist. It's doing much better now and I'm typing with it ;-)
[17:15] <dpm> mhall119, http://developer.ubuntu.com/zh-cn/blog gives me 404
[17:16] <mhall119> as it should, is there a link pointing there?
[17:16] <balloons> I was concerned / afraid I had broken it and didn't have use of it for several weeks
[17:16] <dpm> mhall119, I thought you had added /blog to the navigation
[17:16] <mhall119> dpm: the blog location is https://developer.ubuntu.com/zh-cn/community/blog/
[17:16] <nik90> balloons: you always injure your arm
[17:16] <nik90> glad its all better now
[17:16] <balloons> nik90, I'm abusive.. be nicer to your body
[17:16] <balloons> ty
[17:16] <nik90> :D
[17:17] <nik90> hey I need some help with a MP jenkins failure
[17:17] <nik90> balloons: https://code.launchpad.net/~nik90/ubuntu-clock-app/update-alarm-page-ui-correctly/+merge/246657
[17:17] <AkivaAvraham> brendand, :o lol   I didn't think it'd be this hard. bzoltan_ zbenjamin  -- for the autopilot plugin; it appears that detecting tests is a tad bit hard due to the fact that you can write tests without using the words "autopilot" among other things. Got any suggestions?
[17:17] <nik90> balloons: in the jenkins report, I cannot see the video for some reason..and also the failure is unexpected
[17:17] <dpm> mhall119, ah, on the English site we've got http://developer.ubuntu.com/blog
[17:17] <AkivaAvraham> up until this point, I have been grepping for keywords that would indicate the project has an Autopilot test suite in it.
[17:18] <balloons> AkivaAvraham, technically we encourage authors to layout there directories a certain way
[17:18] <balloons> but if python exists in the project, a __init__.py file exists; that's pretty indicative
[17:18] <balloons> aka, tests/autopilot
[17:18] <mhall119> dpm: the properl location of the english blog is https://developer.ubuntu.com/en/community/blog/
[17:18] <AkivaAvraham> balloons, yah, just not neccessarily needed. i think Ive actually come across some tests that don't have __init__.py
[17:19] <mhall119> /blog/ is there to work around a bug in the zinnia/django-cms plugin
[17:19] <AkivaAvraham> balloons, but the .py is basically neccessary.
[17:20] <mhall119> /blog/ will actually show everything, english and chinese
[17:20] <dpm> ok
[17:20] <balloons> AkivaAvraham, a __init__.py is absolutely required; autopilot runs python packages
[17:20] <AkivaAvraham> perhaps .py and grep "autopilot" should be reasonable enough.
[17:20] <mhall119> I couldn't find a better workaround than this
[17:20] <balloons> so nik90 I see http://91.189.93.70:8080/job/generic-mediumtests-vivid/698/?
[17:20] <nik90> balloons: yup
[17:20] <balloons> and I can see the ogv's
[17:20] <balloons> so?
[17:20] <nik90> the video links dont work
[17:20] <nik90> though
[17:21] <AkivaAvraham> balloons, sec; i'll try to see if I can find the test without an __init__.py
[17:21] <balloons> nik90, I can see them. are you using firefox?
[17:21] <nik90> balloons: no chrome atm
[17:21]  * nik90 tries using firefox
[17:21] <balloons> nik90, yea I remember chrome not supporting embedded ogv's happily
[17:22] <balloons> nik90, you can always download them and run them locally if needed
[17:23] <nik90> ok
[17:29] <bzoltan_> AkivaAvraham: I have not studied yet the issue. No idea what would be the best way to discover autopilot tests of an app.
[17:31] <nik90> balloons: hmm I have an interesting failure point. The AP tests fails to save an alarm while another qml test doing exactly the same, passes.
[17:32] <AkivaAvraham> balloons, blast, it appears you are correct, which is a good thing for me
[17:32] <nik90> balloons: I have created a MP with just the trunk and seeing if the ap tests pass there
[17:33] <balloons> AkivaAvraham, lol, it's funny you would want the opposite; it makes it easy for you to find them
[17:33] <AkivaAvraham> bzoltan_, will you accept the patch if I am able to catch 99% of the tests, ignoring the insane people who decide not to have __init__.py, and actively change their autopilot tests to never include the word "autopilot" at any point?
[17:33] <balloons> nik90, interesting indeed
[17:34] <balloons> nik90, I can generate a trunk run one sec
[17:34] <balloons> no need for an mp
[17:34] <AkivaAvraham> balloons, I'll show you; I'll find happiness in how wrong I was, just so you don't have the satisfaction of being so right.
[17:35] <nik90> balloons: trunk qml tests pass on rtm (utopic) but fail on jenkins (vivid). I have fixed that in the MP I linked before.
[17:35] <nik90> now only the AP tests remain
[17:35] <balloons> AkivaAvraham, that's the spirit. I enjoy being wrong more than being right. (It's a way of coping with the fact you I am wrong so often)
[17:35] <AkivaAvraham> lol
[17:38] <mhall119> beuno: so am I reading this email correct, my application will change from com.ubuntu.developer.mhall119.ureadit to ureadit.mhall119?
[17:38] <mhall119> and does this affect everywhere APP_ID is used, or only click package names?
[17:39] <mhall119> for example, QML apps use APP_ID in their MainView to identify with Mir/Unity what app they belong to
[17:40] <mhall119> and that, in turn, set's the Qt Application class's organizationName and applicationName
[17:40] <beuno> mhall119, it doesn't change, no
[17:40] <beuno> existing apps don't change at all
[17:40] <beuno> new apps, however, will use the new format
[17:41] <mhall119> but just for package name, not anywhere else, right?
[17:42] <mhall119> this seems potentially disruptive, as the APP_ID format was supposed to be the standard used by everything
[17:48] <bzoltan_> AkivaAvraham: Let me see the merge request :) Usually I do not like hackish workarounds ... but let's see
[17:49] <nik90> anyone here running a vivid phone?
[17:51] <bzoltan_> nik90:  me
[17:51] <bzoltan_> nik90:  nexus
[17:51] <nik90> bzoltan_: mind running this MP on your phone and create a repeating alarm? https://code.launchpad.net/~nik90/ubuntu-clock-app/update-alarm-page-ui-correctly/+merge/246657
[17:51] <nik90> bzoltan_: I just rootted my nexus to rtm
[17:52] <bzoltan_> nik90:  ehh... I am running an RTM UITK landing .. so I can not mess around for about 20 hours
[17:52] <nik90> ah ok
[17:52] <nik90> np I'll figure out something
[17:56] <beuno> mhall119, the app namespace
[17:56] <beuno> the APP_ID is based on the namespace
[17:57] <beuno> mhall119, nothing breaks for existing apps or new apps
[17:57] <beuno> no client-side changes needed
[17:57] <beuno> new apps get a different namespace, that's all
[17:58] <mhall119> beuno: they're also in a different order
[17:58] <beuno> mhall119, yeees?
[17:58] <mhall119> it's not <namespace>.<app>, it's <app>.<namespace>
[17:58] <beuno> namespaces are unique strings
[17:58] <beuno> it doesn't matter how they are composed
[17:58] <beuno> it could be a UUID
[17:58] <mhall119> beuno: I'm just saying that the change is going to affect a lot of places
[17:59] <beuno> mhall119, again, I don't understand why at all
[17:59] <beuno> I talked to the SDK folks, to the security folks, click folks
[17:59] <beuno> nobody saw any problems with this, any required changes
[17:59] <mhall119> as long as they're all changed to match, yes
[18:00] <beuno> mhall119, nothing is changed!
[18:00] <mhall119> beuno: eventually you want app developer to use the new format, yes?
[18:00] <mhall119> my com.ubuntu.developer.mhall119.ureadit should eventually be changed to ureadit.mhall119, yes?
[18:08] <balloons> nik90, so how'd it go?
[18:09] <balloons> nik90, this was the trunk run: https://code.launchpad.net/~nik90/ubuntu-clock-app/update-alarm-page-ui-correctly/+merge/246657/comments/609666
[18:10] <nik90> balloons: no that was my proper MP
[18:10] <nik90> trunk run was https://code.launchpad.net/~nik90/ubuntu-clock-app/test-jenkins/+merge/246745
[18:10] <nik90> trunk AP passes...so the failure is related to my MP
[18:11] <balloons> ok, I'm here if you need me
[18:11] <nik90> for some reason, I am not able to run AP tests on my vivid lxc. So I am going to flash my phone to vivid and then try running the tests on it.
[18:11] <nik90> after dinner though
[18:13] <balloons> nik90, would you like me to pull and try locally
[18:13] <balloons> ?
[18:14] <nik90> balloons: sure that would be helpful, atleast then I can verify if it is a jenkins issue or not
[18:14]  * balloons pulls the branch
[18:15] <balloons> running
[18:16]  * nik90 looks eagerly
[18:16] <balloons> ohh right, compiling ;-)
[18:16] <balloons> 1 sec lol
[18:16] <nik90> :)
[18:18] <nik90> just the alarm repeating tests would be sufficient
[18:23] <balloons> it's all running, I assume it'll go somewhat quickly
[18:23] <nik90> ~7 mins
[18:24] <balloons> mmm..  the alarm didn't show after creation.. same as jenkins yes?
[18:26] <beuno> mhall119, did you read my email at all?  :)
[18:27] <balloons> nik90, I get 3 failures
[18:27] <beuno> mhall119, the last 2 paragraphs explain this
[18:28] <balloons> nik90, http://paste.ubuntu.com/9762962/
[18:28] <nik90> balloons: yup
[18:30] <nik90> thnx for running it
[18:30] <nik90> I will have look at my MP to see why no alarm is shown after creation
[18:30] <balloons> nik90, no problem. just ping if you need a re-run, it's simple for me
[18:31] <mhall119> beuno: I did read it, this is the part that concerns me: "In the future, we plan to introduce a one-time migration option that
[18:32] <mhall119> will move over apps with the old-style namespace to the new one"
[18:44] <beuno> mhall119, and what concerns you about that?
[18:44] <beuno> it explains it right after:
[18:44] <beuno> , and
[18:44] <beuno> rename it properly in all installed clients as well, to ensure your
[18:44] <beuno> users aren't affected in any way.
[18:44] <beuno> so the process in the future will migrate it properly
[18:44] <beuno> rename the folders on the device, etc
[18:52] <pmcgowan> nik90, will this be addressed soon? https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354466
[18:57] <mhall119> beuno: I'm concerned that it won't rename everything that needs to be renamed
[18:58] <mhall119> like, things in code
[18:58] <mhall119> beuno: BTW, I'm not trying to criticize the move, just wanting to make sure everything has been thought about
[18:59] <beuno> mhall119, yeah, it won't rename code. You shouldn't hardcode the APP_ID, you should use the API to get it
[19:00] <beuno> mhall119, I get that, yeah. Happy to comb through specifics in case we missed everything
[19:00] <beuno> we haven't fleshed out the rename
[19:00] <beuno> in detail
[19:01] <beuno> it isn't a requirement either for this
[19:01] <beuno> we could keep the old namespaces around forever
[19:02] <beuno> I would prefer not to do it, but we could if it turns out to be impossible
[19:02] <mhall119> beuno: MainView.applicationName is the one I'm most concerned with: https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.MainView/#applicationName-prop
[19:02] <mhall119> some apps may have also hard-coded ContentPeer.appId: https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Content.ContentPeer/#appId-prop
[19:02] <beuno> mhall119, right, that would be a problem
[19:03] <beuno> it'll have to be coordinated with an upload of a new version
[19:03] <mhall119> MainView.applicationName is required, so every QML app has that set to a static string
[19:03] <beuno> because the manifest file will need to point to the new namespace
[19:03] <mhall119> right, and they have to match otherwise Mir/Unity don't like it
[19:03] <beuno> so what would happen is that at some point in the future, we'll ask you to change it, and the review scripts will catch the MainView.applicationName bit
[19:04] <beuno> other hardcoded bits, probably not, but I'm sure it's not hard to grep for it in the review scripts for the transition
[19:04] <mhall119> ok, I think there may already be a review script that checks that they match
[19:04] <mhall119> popey: ^^ do you know for sure?
[19:04] <beuno> mhall119, there is, yes
[19:04] <mhall119> ok
[19:04] <nik90> pmcgowan: hey, that bug is out of my expertise and would require someone with the translation framework knowledge like dpm or tsdegos to help fixing it.
[19:05] <beuno> mhall119, I think the rename is 6-12 months down the line
[19:05] <mhall119> ok, so plenty of time to think of all the potential issues
[19:05] <mhall119> thanks beuno, sorry for being so negative :)
[19:05] <pmcgowan> nik90, ok
[19:05] <beuno> mhall119, totally fine, it's Friday, we all get a pass on Friday!
[19:06] <beuno> I'm a bit tired, we had to push hard to get to this on time  :)
[22:31] <Purebe_|Work> I don't get it
[22:32] <Purebe_|Work> I run a script 1x a minute roughly, it spawns a process in the BG, stores it's PID, does some other stuff, sleeps for 5 seconds and runs pkill on that child PID, and for the first 14 times, every time, it kills the child process
[22:32] <Purebe_|Work> but the 15th time, the child process lives
[22:33] <Purebe_|Work> I don't think I've ever been more confused
[23:55] <Purebe_|Work> Okay
[23:55] <Purebe_|Work> so it has to be
[23:56] <Purebe_|Work> linux has some kind of limit on how many levels deep a process can go
[23:56] <Purebe_|Work> so, it seems to be roughly about 15 processes in and your children PIDs don't work anymore or something
[23:56] <Purebe_|Work> i don't know that seems unlikely but it has to be related to that
[23:57] <Purebe_|Work> except it doesn't make sense as I can still pkill the child process manually
[23:57] <Purebe_|Work> but the parent script can't pkill the child anymore
[23:57] <Purebe_|Work> well that just makes no sense at all