=== thomi_ is now known as thomi === Ursinha-afk is now known as Ursinha === _salem is now known as salem_ === salem_ is now known as _salem === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === jibel_ is now known as jibel === _salem is now known as salem_ === roadmr is now known as roadmr_afk === roadmr_afk is now known as roadmr === Ursinha is now known as Ursinha-afk [15:37] elopio, hey! [15:37] brendand: hello. [15:39] elopio, you know those uitk failures caused by autopilot? [15:40] brendand: the ones for the date picker? [15:40] elopio, yeah === Ursinha-afk is now known as Ursinha [15:54] elopio, brendand I had the date picker failures appear yesterday in jenkins.. magically [15:54] while I was working on this: https://code.launchpad.net/~nskaggs/ubuntu-ui-toolkit/fix-aphelper-emulator-warning/+merge/227093 [15:55] so something changed.. [15:55] if the UITK landed, I would blame that first [15:56] balloons, no - the date changed :) [15:56] balloons, because the test is adding 25 years to this year [15:57] brendand, yes, but depending on how the pickers are implemented they seem to get a large year on them, and when AP reads the list it blows [15:57] balloons, although, i tried changing the date used in the tests and it didn't seem to fix it, so there might be something else going on - or it could be i didn't understand the test properly [15:58] but I've run the UITK tests before without issue [15:58] brendand, yes, it depends on the pickers [15:59] balloons, someone needs to look closer at the tests and see if anything strange is happening === Ursinha is now known as Ursinha-afk [16:35] pitti, perchance you are still about? === Ursinha-afk is now known as Ursinha [16:55] so elopio are you looking at https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1328600? [16:55] Ubuntu bug 1328600 in Autopilot "Autopilot lacks support for large timestamps" [High,Confirmed] [16:56] balloons: not yet. Looking now at the qmlscene crash === Ursinha is now known as Ursinha-afk [16:58] elopio, just wanted to make sure I wasn't stepping on any toes. Is anyone fixing autopilot to support the large timestamps? [16:58] if not, I'll just propose my local change as an mp [16:58] balloons: not yet. Yesterday thomi and veebers were looking at the issues with QML components versions. === rvr is now known as rvrOff === Ursinha-afk is now known as Ursinha === roadmr is now known as roadmr_afk [17:48] elopio, well no matter the date you set, AP sees the 2064 date in the uitk tests [17:49] balloons: that's the max date on the picker, right? [17:50] elopio, that's a question for t1mp I suppose.. It seems we should dig deeper into the UITK. I messed with AP to no avail. The fix in AP also causes some weird off by 1 hour differences. Looking at the qml for the test, modifying the year doesn't fix anything [17:51] balloons: yeah, last time we found that the exception doesn't come from selecting a specific date [17:51] it comes from autopilot trying to load all the properties on the picker. [17:52] elopio, yes I remember.. But I was trying to find a qml solution.. someway to not end up with those high dates in the picker [18:03] balloons: I don't get the hour difference with the statements that veebers pasted there. [18:03] elopio, I don't get it persay either.. I tried it locally and didn't have the issue. However, after I made the change to AP and ran the tests, the differences showed up [18:04] it could be a tz issue, as I get 11 instead of 17 or 18. [18:04] evening balloons elopio [18:04] hello elfy [18:05] elopio, I get 12 :-) so yes, it's tz based [18:05] elfy, good eve to you sir [18:05] elopio: so let's hope that letozaf has seen the hangout and can now tell the difference between us both :) [18:06] you too look slightly different.. I mean it's definitely close :-p [18:06] elfy: I am you! [18:06] oO [18:06] ha ha ha [18:07] * elfy is the young looking one :p [18:08] elopio, so looking at trunk you see they've not touched the datepicker stuff; http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/files/head:/modules/Ubuntu/Components/Pickers/ [18:11] balloons: I suspect this is a lower level change [18:11] like the listview loading more values than before [18:11] ok, I'll dig deeper ;-) [18:12] elopio, that said, I see an interesting idea for a fix... [18:14] balloons: I'm not sure what's the value we are looking for. UTC, or the one on the current tz. [18:14] I actually don't know how to interpret the timestamp if 0 means something different depending on where you are. [18:14] but I think that using timedelta or time is the way to go. [18:18] elopio, so this is I think the easiest way to go forward right away: https://code.launchpad.net/~nskaggs/ubuntu-ui-toolkit/fix-1328600/+merge/227381 [18:20] balloons: well, that will unblock the toollkit landings, but it also changes the API. [18:21] yea, there's a few other things that would have to change as well.. the '50' limit exists a few other places [18:22] elopio, but what I'm really wondering is if we can set this max property in our test qml [18:22] >>> datetime.datetime.utcfromtimestamp(2047570047) [18:22] datetime.datetime(2034, 11, 19, 17, 27, 27) [18:22] >>> datetime.datetime.utcfromtimestamp(0) + datetime.timedelta(seconds=2047570047) [18:22] datetime.datetime(2034, 11, 19, 17, 27, 27) [18:22] that fixes everything.. I think we can, just need to try [18:22] I think that explains to veebers the weird behaviour he was seeing. [18:22] what I don't understand is why he has one call utc, and the other on his timezone. [18:23] balloons: oh, yes, on the tests we can change the max date. [18:24] elopio, yes, syntatically I haven't figured it out tho [18:26] balloons: you need it to be a javascript date object. [18:26] http://developer.ubuntu.com/api/qml/sdk-14.04/Ubuntu.Components.Pickers.DatePicker [18:26] let me find an example. [18:27] elopio, I see setting maximum.. it's just not working [18:29] balloons: this might also fix it [18:29] maximum: Date.prototype.getInvalidDate.call() [18:30] that means infinite, so I guess that the property won't get a big integer. [18:30] maybe -1, or empty. [18:33] mmm.. so I'm still getting that large 50 year date [18:35] I'll try your idea [18:38] mm.. that makes the date max be 2106 :-) [18:40] elopio, so setting the max value I can see the max value, but there are several objects, and the 2064 year object still exists [18:41] hum, I think that we just need to solve it in autopilot [18:41] it's clear that it's autopilot's fault. [18:42] well, I guess that does swing the pendulum back into AP's territory [18:43] elopio, so I wonder if we can look closer at what's really on the dbus tree, vs what AP is creating [18:50] balloons: the vis shows the values before convertion, I think. [18:50] or you can put a breakpoint just before autopilot makes the convertion. I guess you could also inspect dbus, but I'm not sure what to look for there. [18:51] ohh, silly me. I'm doing this all on the phone. [18:51] I can use the desktop, even if it doesn't blow up, to look at the objects [18:51] * balloons facepalms [18:52] elopio, sadly I believe vis shows translated values.. but maybe I'm wrong [18:52] balloons: and it makes it harder to reproduce that our machines are 64bits [18:52] jenkins is 32, so that's why it is failing. [18:53] elopio, i figured out the limit for my box this morning, heh [18:53] elopio, try 91234567891123456789 [18:53] it'll blow up [18:53] here I get an exception when trying the year 10000, but it's not the same exception. === roadmr_afk is now known as roadmr [19:54] elopio, success! I isolated the value from the dbus session [19:57] so one object has the maximum date I set, while the other still has the default maximum [19:58] balloons: so there are two pickers? I'm not sure what you meant [19:59] elopio, I'm playing around looking at the dbus session. It's not an autopilot thing. It's definitely in the toolkit [19:59] I'm looking at the raw values AP is reading, and it's in there [19:59] elopio, here's one of the objects: http://paste.ubuntu.com/7816047/ [20:00] so let me try the fix now :-) [20:00] woot === Ursinha is now known as Ursinha-afk [20:02] elopio, TLDR, setting the max works. But you also have to set the max for the timepicker [20:03] because it too has m/d/yyyy on it === Ursinha-afk is now known as Ursinha [21:53] what is this channel for exactly? I see unicorns... but that does not exactly tell me much... [21:53] Aki-Thinkpad, this is for the quality team [21:53] testing, bugs, fun stuff [21:54] balloons, ahhh; okay. === salem_ is now known as _salem === _salem is now known as salem_ === salem_ is now known as _salem