**** BEGIN LOGGING AT Fri Feb 05 02:59:59 2016 Feb 05 08:19:13 Morning Feb 05 08:20:13 Garfonso: I agree, but we should also keep the compatibility with a QML loading Feb 05 08:20:33 morning Tofe Feb 05 08:21:06 Which isn't necessarily an issue, if we organize the files correctly and we point to the loadable-frameworks from QML Feb 05 08:23:40 maybe a package.json with the right content is already sufficient: https://nodejs.org/api/modules.html#modules_folders_as_modules Feb 05 08:23:42 (and of course you're completely correct about the numberParamType typo) Feb 05 08:24:04 ;) Feb 05 08:24:29 just saw it in the diff and thought that's probably an oversight that can cause a hard to find bug later... Feb 05 08:24:48 yep Feb 05 08:25:07 anyway I didn't really want to merge it as-is, it's more a WIP Feb 05 08:27:27 morning Feb 05 08:34:10 Tofe: So for now we should include Garfonso's PR but not yours since it's WIP? Feb 05 08:35:23 Tofe: not sure what you are doing there. You try to replace legacy phonenumber handling with something new? Feb 05 08:36:21 Garfonso: Yeah Feb 05 08:37:10 Because legacy is outdated with it's numberplan & mapping & limited to 20 or so countries. While new one is up2date based on Google's work & 180 countries or so? Feb 05 08:40:32 Garfonso: This is for the geolocation lookup. So +49 30 will show Berlin etc Feb 05 08:42:16 Garfonso: And it was quite a pain to get g11n working in QML due to the dependencies as well ;) Feb 05 08:44:25 So a simple straight forward library is the way to go, both myself and Tofe thought and we'll plug that into the Enyo/legacy bits to replace the outdated one there. Feb 05 08:47:44 Herrie|Veer: not only geolocation, but also normalizing of phone number, which I need in the phone app Feb 05 08:49:10 Tofe: Right, but those 2 go hand in hand, don't they? You can't really do proper normalization without the geolocation, or can you? Feb 05 08:55:24 well, the common part is the geocoding, where the +46 will get you to sweden and then you'll decode the phone number as a swedish one Feb 05 08:55:51 But I'm being picky; we do agree. Feb 05 08:56:11 Tofe: LOL :P Feb 05 08:59:45 Tofe: So your PR is not merge worthy yet? Feb 05 09:05:11 Herrie|Veer: no, not at all Feb 05 09:05:41 and I doubt this "fallback on old g11n" thing is a good idea Feb 05 09:05:59 better only have one normalize format Feb 05 09:09:00 Tofe: Yeah I agree Feb 05 09:09:10 Just need to know what to include in release :P Feb 05 09:09:21 We're now still at the 5s phone app loading :P Feb 05 09:10:20 Herrie|Veer: oh, are we ? but phone depends on phonenumber.js now Feb 05 09:11:19 Tofe: hmmmz Feb 05 09:11:29 Let me see maybe I forgot to bump something Feb 05 09:11:40 luneos-components maybe Feb 05 09:12:16 Nope Feb 05 09:12:29 Both phone & luneos-components are at latest Feb 05 09:15:06 Tofe: Must have been first boot Feb 05 09:15:10 On 2nd boot it's OK Feb 05 09:15:35 ok Feb 05 09:15:49 Tofe: yes, remove the fallback... also I'm very much for using something new for phone number normalization and get rid of contacts lib all together Feb 05 09:15:58 (maybe keep the vcard handling) Feb 05 09:16:39 Garfonso: I don't have the necessary knowledge to handle a removal or big rework of contacts lib, but I can replace the normalize handling Feb 05 09:17:11 I'll remove the fallback tonight, then Feb 05 13:52:52 JaMa: ping Feb 05 13:56:55 pong Feb 05 13:58:23 Had a Grouper testing build fail but we didn't change anything specific for Grouper. Can you have a look? Maybe out of space again? Feb 05 14:00:48 sure Feb 05 14:01:08 grouper or maguro? Feb 05 14:01:35 there is ICE in latest maguro build Feb 05 14:02:05 Sorry maguro :P Feb 05 14:02:14 possibly hw issue Feb 05 14:02:19 We didn't change anything machine specific afaik Feb 05 14:02:29 I've retriggered th build Feb 05 14:02:46 JaMa: OK if it fails again we need ka6sox? Feb 05 14:03:18 yes, nothing interesting in log Feb 05 14:03:28 but it could be faulty ram or something like that Feb 05 14:03:39 I've seen couple ICEs lately on aruba as well Feb 05 14:03:42 Or faulty HD? Feb 05 14:06:00 JaMa: Unstable mako still bootlooping (as expected) Feb 05 14:06:31 Tofe will look into the other issues for Tenderloin & Maguro (probably root caused by PulseAudio) Feb 05 14:09:08 Audio doesn't work on those, lunawebappmgr crashes but seems linked to PulseAudio as well. Feb 05 14:09:25 So might be that fixing PulseAudio will fix that too. Feb 05 14:21:09 Herrie|Veer: speaking of which, I've seen similar pulseaudio complaints on my current N4 image; so maybe I was on the wrong track Feb 05 14:22:55 Tofe: Yeah but since PA doesn't recommend it anyway it might be good to use their recommendation? Feb 05 14:26:17 JaMa: Seems it failed again... Feb 05 14:29:01 Herrie|Veer: yes, but not until we fix the issue, otherwise it will just introduce more differences with the working image Feb 05 14:31:23 Tofe: OK. Feb 05 14:32:06 now the error is different Feb 05 14:32:09 strange one Feb 05 14:32:12 | ERROR: Required kernel image is not available as fastboot image! /home/jenkins/workspace/luneos-testing/webos-ports/tmp-glibc/deploy/images/maguro/zImage-maguro.fastboot doesn't exist. Feb 05 14:32:39 I'll clean the workspace that will fix it, but we probably miss the dependency Feb 05 14:41:30 what is the issue? Feb 05 14:42:55 gcc is quite often failing with ICE Feb 05 14:43:06 we haven't changed gcc lately Feb 05 14:49:12 what version are we using? Feb 05 14:52:23 of gcc? Feb 05 14:52:53 49 Feb 05 14:59:23 I've had issues with 5 but not 4.9 Feb 05 15:26:24 Tofe: your meta-webos-ports commit 923d9b0b breaks build with newer qtwebengine, was there some reason why you overwrite EXTRA_QMAKEVARS_PRE instead of appending to it? Feb 05 15:35:02 JaMa: one moment Feb 05 15:36:38 JaMa: no, it's just a mistake Feb 05 15:40:22 ok, will push a fix Feb 05 15:41:24 ok thanks :) Feb 05 15:51:16 nizovn: ping Feb 05 15:51:55 Herrie|Veer: pong Feb 05 15:52:26 nizovn: You need any more info for mediaindexer? Feb 05 15:52:38 Or you're OK with what you have now? Feb 05 15:52:55 For testing you can sideload legacy music app IPK and see if it works :) Feb 05 15:53:09 Just put some MP3 files on media/internal :P Feb 05 15:55:06 And the kinds will be pretty much instantly populated Feb 05 15:55:32 i'm ok with that, for now i'm thinking how to find offset of apic in mp3 file Feb 05 15:55:54 nizovn: The code I quoted in issue should be able to do that? Feb 05 15:56:01 Quite sure taglib somehow supports it Feb 05 15:56:44 The rajeevandlinux link Feb 05 16:00:10 i can't find offset in docs, maybe looking in the wrong place Feb 05 16:08:34 nizovn: Yeah it's not easy to find :P Feb 05 16:09:14 Tofe: did small luna-systemui PR to fix error in log. Basically calling a method that wasn't released in OWO :P Feb 05 16:27:17 nizovn: Ah seems taglib doesn't provide the offset? Feb 05 16:27:26 I guess that would need to be hacked in somehow? Feb 05 16:28:30 probably, i will read more about id3v2 Feb 05 16:31:49 nizovn: You should check attachedpictureframe.cpp Feb 05 16:32:01 parseFields has a pos Feb 05 16:32:11 Which is probably what you're looking for Feb 05 17:53:02 Garfonso: ping Feb 05 18:05:59 Herrie: am i right that we need something called "extractfs"? seems it's used in com.palm.app.musicplayer/utility/utilities.js in getTrackImage function Feb 05 18:29:53 nizovn: I haven't been that far yet Feb 05 18:29:55 Let me check Feb 05 18:45:19 Herrie: I'm going to setup a bunch of PR for phonenumberlib, but I'd like to wait for Garfonso to tell me if it seems ok; and I still need to test it properly on device Feb 05 18:46:03 Tofe: OK Feb 05 18:46:21 I'm looking into some warnings & errors in logs and clearing those out Feb 05 18:48:39 Tofe: Pong Feb 05 18:50:46 Garfonso: I've sketched up a "phonenumberlib" loadable framework Feb 05 18:50:54 one moment, I'm going to push it to GH Feb 05 18:52:17 Garfonso: I've now update my PR: https://github.com/webOS-ports/loadable-frameworks/pull/5 Feb 05 18:52:45 should it work ? especially the require in contacts' prologue.js Feb 05 18:54:26 Herrie: my PRs are now in place (meta-webos-ports, loadable-frameworks and luneos-components) Feb 05 18:55:17 Herrie: it's completely not tested :p Feb 05 19:13:14 the require should work, from what I know. Feb 05 19:37:51 nizovn: https://bpaste.net/show/63db47bba13b that's the contents of /usr/palm/services/filenotifyd-triton/motes/image.js on 3.0.5 Feb 05 19:43:40 Herrie: so we need to use extractfs? i think it will take some time to implement it Feb 05 19:45:08 nizovn: It's basically a path Feb 05 19:45:13 I think we might have it already Feb 05 19:45:18 If not we can create it Feb 05 19:45:29 Not sure what extractfs does as an app or service :S Feb 05 19:46:08 nizovn: Ah it seems to be some embedded image extractor: Description: Palm embedded file extractor Feb 05 19:46:16 So I guess taglib does the same already Feb 05 19:46:31 Herrie: seems it's fuse filesystem, you can see it in mount output Feb 05 19:47:19 extractfs on /var/luna/data/extractfs type fuse.extractfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0) Feb 05 19:48:03 nizovn: OK so that might prove tricky for now :S Feb 05 19:48:25 Maybe focus on the other kinds first? Those should be fairly straigt forward right? Feb 05 19:49:32 not sure, i haven't looked at them yet Feb 05 19:49:57 nizovn: This is the legacy code that generates them: /usr/palm/services/filenotifyd-triton/filenotifyd_module_audio.js Feb 05 19:49:58 but i'm newbie on db stuff Feb 05 19:51:24 nizovn: db8 is pretty easy in general ;) Feb 05 19:52:19 https://developer.lge.com/webOSTV/develop/web-app/app-developer-guide/db8/webos-db8-basics/ Feb 05 19:54:00 ok Feb 05 19:55:35 We're basically putting a lot of strings in a db kind Feb 05 19:55:47 Which you can see as a table in a SQL db Feb 05 20:01:29 nizovn, Herrie: It shouldn't matter where the thumbnail images reside. There is no real need for a new partition or similar. Feb 05 20:04:51 Garfonso: Just legacy and some other apps might expect it at extractsfs location Feb 05 20:04:56 Like music app appearantly Feb 05 20:04:59 Garfonso: those thumbnails are embedded in mp3 file. and seems that virtual fs magically can retrieve them based on path, offset and size Feb 05 20:20:28 Herrie, Nizonn, FWIW, "Triton" was the name of the custom background-task-runner that was ditched in favor of Node. So, if a file has Triton in the name, check to see if it was really being used. Feb 05 20:24:54 HoloIRCUser1: (AKA DougReeder :P): Yeah but it seems it was still used for filenotifyd (mediaindexer in 3.0.5) Feb 05 20:25:03 But then as nodeJS variant ;) Feb 05 20:27:22 Herrie, did you solve the gcc ICEing up issue? Feb 05 20:27:34 ka6sox: Rerunning it solved it Feb 05 20:27:43 Strange it happens randomly lately though Feb 05 20:27:58 :/ Feb 05 20:28:52 Ok, then :-) Feb 05 20:35:18 nizovn: yeah, but if it's easier for us to extract them and save as image files somewhere in var or so, then why not do that? Feb 05 20:35:54 Herrie: yeah, but that's bad design. Apps should only rely on the path for the thumb that mediaindexer gives them. Feb 05 20:36:55 Garfonso: Yeah that's true Feb 05 20:50:46 Garfonso: i agree, but we will not be compatible with some legacy apps then **** ENDING LOGGING AT Sat Feb 06 02:59:58 2016