--- Log opened Mon Jan 08 00:00:03 2018 00:11 -!- Horwitz [~mich1@p200300800E226600022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 00:24 -!- Horwitz [~mich1@p200300800E0DDA00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 00:24 -!- mode/#navit [+o Horwitz] by ChanServ 00:39 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n 00:39 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed 00:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html 00:46 -!- pmckinley [~Peter_McK@88-110-207-109.dynamic.dsl.as9105.com] has joined #navit 00:47 -!- pmckinley [~Peter_McK@88-110-207-109.dynamic.dsl.as9105.com] has left #navit [] 01:44 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 248 seconds] 01:50 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 04:24 #navit: <+jkoan> KaZeR: in my opinion installing an apk directly is not a good solution because of two reasons. Reason one is its not very user friendly (download, enable unknown sources, install it, and optional disable unknown sources) and reason two, updates. The biggest issue in my eyes are the updates not only because of the not features, the newer versions will also have Bugfixes for important issues and sometimes also the bin file format can change (eve 04:24 #navit: <+jkoan> …be unusable, and the user will not know why because he is never told that the is a updated version 04:26 #navit: <+jkoan> But even though we should also publish a "directory index" for the apks and probably also all other files on the repos. I hope to get them up soon. 04:48 -!- noradtux_ [~noradtux@port-54479.pppoe.wtnet.de] has joined #navit 04:48 -!- noradtux [~noradtux@port-18428.pppoe.wtnet.de] has quit [Ping timeout: 265 seconds] 04:48 -!- noradtux_ is now known as noradtux 05:11 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 05:11 -!- mode/#navit [+v xenos1984] by ChanServ 05:27 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 248 seconds] 05:35 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 07:23 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 265 seconds] 09:34 -!- nuovolnx [~nuovolnx@host13-30-dynamic.33-79-r.retail.telecomitalia.it] has joined #navit 09:50 -!- nuovolnx [~nuovolnx@host13-30-dynamic.33-79-r.retail.telecomitalia.it] has quit [Quit: Leaving] 10:32 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit 10:32 -!- mode/#navit [+v xenos1984] by ChanServ 12:00 -!- nuovolnx [~nuovolnx@host127-72-dynamic.7-87-r.retail.telecomitalia.it] has joined #navit 12:37 -!- nuovolnx [~nuovolnx@host127-72-dynamic.7-87-r.retail.telecomitalia.it] has quit [Remote host closed the connection] 14:03 -!- rdo [~rdo@mail.bokomoko.de] has joined #navit 15:00 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.] 15:48 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 15:48 -!- mode/#navit [+v xenos1984] by ChanServ 16:52 -!- ZeroOne [~ZeroOne@91.114.11.118] has joined #navit 17:29 -!- ZeroOne [~ZeroOne@91.114.11.118] has quit [Read error: Connection reset by peer] 17:30 #navit: <@KaZeR> hi there 17:30 #navit: <+jkoan> hi KaZeR 17:30 #navit: <@KaZeR> 'sup jkoan ? 17:31 #navit: <+jkoan> having dinner :D 17:32 #navit: <@KaZeR> having breakfast here :) enjoy! 17:32 #navit: <+jkoan> time zones are annoying :D 17:40 #navit: <@KaZeR> true 17:45 #navit: <+jkoan> whats on your todo for today? 18:09 #navit: <@KaZeR> couple of things non navit related to start. maybe some work on the qml2 ui. I recently integrated a virtual keyboard, but city search is behaving weirdly 18:11 #navit: <@KaZeR> btw, here's a recent pic of my setup in the car : https://imgur.com/a/RdU5t 18:12 #navit: <+jkoan> i like the 3d printed path :D 18:16 #navit: <+ilovekiruna> hi KaZeR, hi jkoan 18:16 #navit: <+jkoan> Hi ilovekiruna 18:17 #navit: <+ilovekiruna> jkoan: u saw my PMs from yesterday 18:18 #navit: <+jkoan> oh no, i missed them :X 18:25 #navit: <@KaZeR> jkoan: yeah :) still need to add a finishing layer. but mechanically it works as expected 18:25 #navit: <@KaZeR> hey ilovekiruna 18:32 #navit: <+ilovekiruna> KaZeR: I was experiencing the same bug during my holidays again 18:33 #navit: <+ilovekiruna> jkoan: what do you think of expanding the testing setup for navit a bit? 18:33 #navit: <@KaZeR> ilovekiruna: which one? 18:33 #navit: <+ilovekiruna> KaZeR: that no route was found 18:33 #navit: <+ilovekiruna> plus i saw that navit too insane long routes :( 18:34 #navit: <+ilovekiruna> even with the shortest route profile 18:34 #navit: <+jkoan> ilovekiruna: which testing setup specific? 18:34 #navit: <+ilovekiruna> jkoan: own device farm 18:34 #navit: <+ilovekiruna> jkoan: wondering if we could make it more a HiL setup 18:35 #navit: <+ilovekiruna> jkoan: appium, plus sensor data via adb or sth similar 18:36 #navit: <+jkoan> the rest of the day i want to try to bring the repos up (build docker images to provide apt and fdroid ) 18:36 #navit: <+jkoan> do you want to help? 18:41 #navit: <@KaZeR> ilovekiruna: do you have logs? this is weird 18:45 #navit: <+jkoan> KaZeR: only as a notice i will make some commits to the Dockerfiles Repo, but its not ready right now 18:46 #navit: <@KaZeR> jkoan: as long as you don't overwrite the image tag it should be fine 18:47 #navit: <+jkoan> i cant overide the image tag because sou set it over docker hub where i dont have full rights 18:48 #navit: <+jkoan> KaZeR: you didn’t set up automated builds right? 18:49 #navit: <@KaZeR> jkoan: i can grant you permission to docker hub, no worries. We don't have automated builds yet for the docker images indeed 18:51 #navit: <+jkoan> yes, i know i have the rights on hub.docker.com but there permission system is wired. because i cant setup automated builds (probably that was due to the acces to private repos of navit org which is really wired) 18:54 #navit: <+jkoan> KaZeR: do you see the problem? :D https://imgur.com/wJO5GzZ 18:57 #navit: <@KaZeR> well hub.docker.com is only a image repository, you can't build images from there. we need to use circleci to do that 18:57 #navit: <+jkoan> thats false 18:57 #navit: <@KaZeR> ha! :) 18:58 #navit: <+jkoan> see here: https://hub.docker.com/add/automated-build/navit/github/orgs/ there you should have navit, right? 18:59 #navit: <+jkoan> (on the left) 19:00 #navit: <@KaZeR> "You haven't linked to GitHub or Bitbucket yet." interesting. i wasn't aware that they had that feature 19:01 #navit: <+jkoan> for example this one https://hub.docker.com/r/jkoan/spigot/ is automated, it builds when i push something to the responding git repo 19:03 #navit: <+ilovekiruna> KaZeR: I guess i can replicate it also from distance 19:03 #navit: <+ilovekiruna> just need to set current position 19:04 #navit: <+ilovekiruna> during xmas didntmanage to activate logs :( 19:04 #navit: <@KaZeR> jkoan: cool! i'm trying to weight the pros and cons of using circleci vs dockerhub to build. Thoughts? 19:04 #navit: <+jkoan> ilovekiruna: same here, i had read all logs this morning in the tram 19:05 #navit: <+ilovekiruna> jkoan: waht do u think of such a bit "advanced" setup? 19:05 #navit: <@KaZeR> ilovekiruna: well that'll be a start, although logs could be useful. Can you share your navit.xml ? 19:05 #navit: <@KaZeR> ilovekiruna: advanced setup? 19:05 #navit: <+ilovekiruna> KaZeR: check my message earlier 19:05 #navit: <+ilovekiruna> about more like a HiL setup 19:05 #navit: <+jkoan> KaZeR: dockerhub is better because most people searching for automated builds and its more direct 19:06 #navit: <+jkoan> (and does not block the resources of circleci) 19:09 #navit: <@KaZeR> ilovekiruna: if all you want is to replay the track, navit or gpsd can do that already 19:09 #navit: <@KaZeR> jkoan: good point. One point in favor of circleci though is that we can do more than just build the image : we can test if the compilation work too. Not pushing one way or another, just thinking 19:09 #navit: <+ilovekiruna> KaZeR: that was the idea, but not just to use gps 19:09 #navit: <@KaZeR> one point also if favor of dockerhub is that it makes the Dockerfile visible 19:10 #navit: <+ilovekiruna> that approach is a bit limited ;-) 19:10 #navit: <@KaZeR> ilovekiruna: what else you'd you like? 19:10 #navit: <+ilovekiruna> for example accelerometer data 19:12 #navit: <@KaZeR> i see. we don't use that data today though :) 19:13 #navit: <+ilovekiruna> or compass 19:13 #navit: <+ilovekiruna> KaZeR: it was also meant more to enable us to implement more advanced sensors 19:14 #navit: <+ilovekiruna> KaZeR: plus, it could be sth cool that would be a bit outside what is availabe FOSS so far for GPS testing, so maybe nice extension for next year's fosdem 19:14 #navit: <+jkoan> @all who is going to visit FOSDEM? ilovekiruna and i will visit it and i want to know if anybody is joining us 19:15 #navit: <@KaZeR> can't make it this year, sorry guys :) next year i'll try to schedule my usual trip to France at that time 19:18 #navit: <+jkoan> i will try to make it possible to make a time-laps and enable the gps recording ;) 19:20 #navit: <+jkoan> also i ordered a gps module for my laptop (MiniPCIe slot) 19:21 #navit: <@KaZeR> jkoan: timelapse? from where? 19:22 #navit: <@KaZeR> also, interesting choice to go miniPCIe. Why not USB? (just curious) 19:22 #navit: <+jkoan> way to fosdem with navit 19:22 #navit: <@KaZeR> oh right we discussed that 19:23 #navit: <+jkoan> because it its only 7g and can be nicely build in the pc itself 19:25 #navit: <@KaZeR> i see 19:25 #navit: <+jkoan> and the slot is free anyway 19:26 #navit: <@KaZeR> so, are you all set for the trip? 19:27 #navit: <@KaZeR> ilovekiruna: want to look into your logging issue? 19:27 #navit: <+jkoan> mostly, i dont know how i will record the video :D but the rest is good yes 19:27 #navit: <@KaZeR> well if you have the laptop, a USB cam with a script should be easy. We could even geotag each captured image with your actual position 19:28 #navit: <+jkoan> the biggest problem will be the power, i dont have a laptop car cable and no 230V converter 19:29 #navit: <@KaZeR> what's your laptop? 19:29 #navit: <+jkoan> T430 19:29 #navit: <+jkoan> lenovo thinkpad sorry ^^ 19:31 #navit: <+ilovekiruna> KaZeR: which logging issue do you exactly mean? 19:32 #navit: <+jkoan> but i think i will find a solution, i have enough things here. last solution would be a Canon DSLR with interval capature or something like that, i will see 19:33 #navit: <@KaZeR> that sounds bulky :) 19:33 #navit: <@KaZeR> ilovekiruna: you mention not having logs because something wasn't working as expected 19:33 #navit: <+ilovekiruna> KaZeR: no, i simply didnt have logs, because i think i didnt activate it 19:33 #navit: <@KaZeR> ha! ok 19:35 #navit: <+ilovekiruna> KaZeR: what was strange, via google maps it is around 670 km from Torun to Celle 19:35 #navit: <+ilovekiruna> KaZeR: navit suggested a route of 850 km 19:35 #navit: <+ilovekiruna> also in the profile shortest route 19:35 #navit: <+ilovekiruna> only the pedantic profile should sth similar to google 19:37 #navit: <+ilovekiruna> KaZeR: i can reproduce that right now 19:38 #navit: <@KaZeR> ilovekiruna: perfect use case for https://github.com/navit-gps/routing-qa :) 19:39 #navit: <+ilovekiruna> KaZeR: can i commit directly to there? 19:41 #navit: <@KaZeR> yeah, this repo has been underused for some time. it needs a refresh/upgrade anyway :) 19:41 #navit: <@KaZeR> the end goal was to have the maps displayed at http://navit-gps.github.io/routing-qa/ but i never finished it 19:42 #navit: <@KaZeR> we have a lot more test cases in branches if you need more examples 19:54 #navit: <+ilovekiruna> KaZeR: can u give me a short hint again about how to convert the coordinates? 19:56 #navit: <+ilovekiruna> the digits after the "." are considered decimal, right? 19:58 #navit: <@KaZeR> correct 19:59 #navit: <@KaZeR> you want to convert the coordinates between decimal and minutes? or to navit's coordinates? 20:00 #navit: <+ilovekiruna> the file format seems to be just decimal 20:00 #navit: <+ilovekiruna> but figured out now 20:00 #navit: <+ilovekiruna> how about the format of commit messages? 20:01 #navit: <+ilovekiruna> KaZeR, jkoan: When should we pick up the compiler warning issue again? 20:01 #navit: <+jkoan> definitely but not today for me :X 20:01 #navit: <@KaZeR> ilovekiruna: there's no specific commit message format for that repo 20:03 #navit: <@KaZeR> btw, we have a stub of documentation for that QA repo ilovekiruna : https://wiki.navit-project.org/index.php/QA feel free to expand with what you'll learn :) 20:07 #navit: <+ilovekiruna> KaZeR: pushed the coordinates 20:08 #navit: <+jkoan> ilovekiruna: build is running, curious to see whats happening: https://circleci.com/gh/navit-gps/routing-qa/236 20:09 #navit: <@KaZeR> so one thing that we need to do with that repo is to use an image that we would build from trunk instead of rebuilding everything. Would make the test faster 20:16 #navit: <+ilovekiruna> KaZeR: driving along the shorter route, I noticed that using all car profiles except pedantic, navit was pretty stubborn 20:16 #navit: <+ilovekiruna> wanted me to turn around and use the long route 20:16 #navit: <+ilovekiruna> pedantic didnt converge to any route 20:17 #navit: <+ilovekiruna> maybe u can give some insights about the differences between the profiles 20:18 #navit: <@KaZeR> i think that the behavior in "shorter" is because if you miss a turn using that profile, navit avoids recalculating if possible and tries to send you back to the missed turn instead. You can tweak the turnaround penalty to affect the behavior 20:18 -!- AVIC-MRZ02 [b9e3b688@gateway/web/freenode/ip.185.227.182.136] has joined #navit 20:18 #navit: <@KaZeR> No route found, last status : 1, duration : 50.1585960388 -> so we can reproduce your issue in the CI 20:18 #navit: <@KaZeR> hey AVIC-MRZ02 20:18 #navit: < AVIC-MRZ02> Hi KaZeR 20:19 #navit: <+jkoan> hi AVIC-MRZ02 20:19 #navit: <+ilovekiruna> hi AVIC_MRZ02 20:19 #navit: < AVIC-MRZ02> Hi jkoan 20:19 #navit: < AVIC-MRZ02> Hi ilovekiruna 20:24 #navit: < AVIC-MRZ02> KaZeR: I couldn't manage to modify registry. "Regflushkey" code is running (I'm sure because flush version of navit is working) but after re-start the keys remains the same. 20:25 #navit: <@KaZeR> mmm. are you able to check the keys after they are supposed to have been flushed? 20:25 #navit: < AVIC-MRZ02> Yes. I can run regedit.exe 20:26 #navit: < AVIC-MRZ02> First, I'm changing the keys, then I'm applying flush, then I'm checking registry keys and finally re-start. 20:27 #navit: < AVIC-MRZ02> After re-start, all keys return back to it's original. 20:31 #navit: <+ilovekiruna> jkoan: where should i see the reults from the build? 20:33 #navit: <+jkoan> i thought here, but its not the case http://navit-gps.github.io/routing-qa/ 20:41 -!- charles__ [48241adf@gateway/web/freenode/ip.72.36.26.223] has joined #navit 20:42 #navit: <@KaZeR> AVIC-MRZ02: but after applying and before restarting, are the keys flushed as expected? 20:42 #navit: <@KaZeR> ilovekiruna: there's no results because the routing failed 20:44 #navit: < AVIC-MRZ02> KaZeR: After applying and before restarting I'm checking the keys if they are changed. But how I'll be sure that they are flushed? 20:45 #navit: < charles__> Howdy. 20:46 #navit: < charles__> Pull Request 390 seems to have hit a problem. 20:51 #navit: <+ilovekiruna> KaZeR: i dont see my Poland.yaml on the website http://navit-gps.github.io/routing-qa/ 20:57 #navit: <@KaZeR> ilovekiruna: look at the third entry of the step "$ python test.py $CIRCLE_ARTIFACTS $CIRCLE_TEST_REPORTS "metric" here : https://circleci.com/gh/navit-gps/routing-qa/236#artifacts/containers/0 20:58 #navit: <@KaZeR> routing failed, so no output yaml was generated 20:59 #navit: <@KaZeR> charles__: thanks for the nudge. /root/project/navit/command.c:1019:1: internal compiler error: Segmentation fault : looks like a ci issue. going to restart it 20:59 #navit: <@KaZeR> (it = the job ) 21:00 #navit: <@KaZeR> AVIC-MRZ02: how do you change the keys? 21:04 #navit: <+ilovekiruna> KaZeR: what is the meaing of the three links in that log? 21:09 #navit: <@KaZeR> ilovekiruna: this is to compare Navit's routing with other routing engines 21:09 #navit: < AVIC-MRZ02> KaZeR: I found a scripting language called 'Mortscript'. All the commands are written in a text file and simply 'Mortscript.exe' takes these command from file and performs them. 21:10 #navit: <@KaZeR> AVIC-MRZ02: ok. that script cannot flush the keys? 21:10 #navit: < AVIC-MRZ02> There is a command to change registry keys, I'm using that command. After using the command I'm running regedit.exe to be sure that keys are changed. 21:11 #navit: < AVIC-MRZ02> KaZeR: I couldn't find such a command to flush the keys. 21:12 #navit: <+ilovekiruna> KaZeR: both failed cases have as time around 50 seconds. Is there a timeout in the code? 21:12 #navit: <@KaZeR> my concern is that the content of the registry could be read from nand at boot time. so basically, be read only outside of a given session. if it's the case the only way to make this permanent is to run a script at each boot 21:15 #navit: < AVIC-MRZ02> KaZeR: Running a script at each boot is not making it permanent but changing the keys to whatever we want in each boot. Isn't it? 21:15 #navit: <@KaZeR> ilovekiruna: i don't recall having a timeout on the routing. I think it's more that it takes 50s on the CI to explore the full graph 21:15 #navit: <@KaZeR> AVIC-MRZ02: correct 21:16 #navit: < AVIC-MRZ02> KaZeR: But this script must be executed before OS reads the values of registry, otherwise it'll be useless. 21:20 #navit: < AVIC-MRZ02> KaZeR: And reading registry is one of the leading tasks of the OS. 21:22 #navit: <@KaZeR> ha i see, i thought that you were trying to set a key required for an app. that's different. what you actually need could be tricky 21:23 #navit: <@KaZeR> ilovekiruna: also our current QA code is using the default routing profile. we might need to expand our test code to handle other profiles 21:24 #navit: < AVIC-MRZ02> KaZeR: It's getting expensive :)), There must be a script written in assembly and located in boot sequence :P 21:27 #navit: <@KaZeR> charles__: PR merged, thanks! 21:31 #navit: <@KaZeR> AVIC-MRZ02: well i think that all of the OS part is read from NAND but never written back. Have you been able to make some other changes permanent? 21:35 #navit: < AVIC-MRZ02> KaZeR: I didn't check if a can change another key of registry. It is possible to copy files to nand or change files BUT I'm not sure if this is the entire nand or just a portion which is allowed to see. 21:36 #navit: < AVIC-MRZ02> On the other hand, all registry values must be kept in a file or bunch of files physically, and it's not possible to find this information. 21:37 #navit: <@KaZeR> yeah, this registry thing is really stupid 21:39 #navit: < AVIC-MRZ02> And other stupid thing is this, Windows CE and PC versions of Windows are totally different. It seems they are alike but they are not. 21:41 #navit: < AVIC-MRZ02> Logically it must be possible to use old-native MFC on WinCE also, because it is the graphical foundation of Microsoft BUT it is not possible 21:42 #navit: < charles__> KaZeR: Thx. 21:45 #navit: < AVIC-MRZ02> Why if there's such a foundation in hand that can run on 32 bits, not used in mobile OS versions. It's strange. 21:47 #navit: <@KaZeR> probably because of hardware restrictions, like the fact that CE uses ARM processors 21:51 #navit: < AVIC-MRZ02> May be. 21:52 #navit: < AVIC-MRZ02> Ops. Now I have to leave. See you all soon. 21:53 -!- AVIC-MRZ02 [b9e3b688@gateway/web/freenode/ip.185.227.182.136] has quit [Quit: Page closed] 22:03 -!- ColdFyre_ is now known as ColdFyre 23:34 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 248 seconds] 23:49 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit 23:54 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] --- Log closed Tue Jan 09 00:00:04 2018