--- Log opened Wed May 09 00:00:13 2018
04:38 -!- noradtux [~noradtux@2a04:4540:8c02:1d01:69db:5f48:a8d8:b6f5] has quit [Ping timeout: 265 seconds]
04:43 -!- noradtux [~noradtux@port-18187.pppoe.wtnet.de] has joined #navit
04:50 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
04:50 -!- mode/#navit [+v xenos1984] by ChanServ
05:04 -!- naggety [~naggety@32.red-81-47-78.dynamicip.rima-tde.net] has quit [Ping timeout: 240 seconds]
05:05 -!- naggety [~naggety@186.red-80-27-241.dynamicip.rima-tde.net] has joined #navit
06:40 #navit: <+jkoan> KaZeR: Facebook stats gone even better noch answer rate 100% and reaction time 2min
06:42 #navit: <+jkoan> And we already got ~160 stars on GitHub :O when did the last 60 came?!
06:44 #navit: < naggety> Hi jkoan, hi all
06:44 #navit: <+jkoan> Hi naggety
06:44 #navit: < naggety> What's up? I'm reading you are in a very good moment!
06:46 #navit: <+jkoan> Currently day work
07:18 #navit: < naggety> How does the project go?
07:18 #navit: < naggety> KaZeR: are you online?
08:00 -!- ColdFyre__ [~lenny@172.92.43.110] has quit [Ping timeout: 256 seconds]
09:55 -!- bzed [~bzed@shell.bzed.at] has quit [Ping timeout: 248 seconds]
10:02 -!- bzed [~bzed@shell.bzed.at] has joined #navit
11:34 -!- aerostitch [~aerostitc@c-67-164-55-119.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds]
12:06 -!- aerostitch [~aerostitc@c-67-164-55-119.hsd1.ca.comcast.net] has joined #navit
12:24 -!- aerostitch [~aerostitc@c-67-164-55-119.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds]
13:31 -!- twoelk [~twoelk@p5DC8734B.dip0.t-ipconnect.de] has joined #navit
14:17 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
14:35 -!- twoelk [~twoelk@p5DC8734B.dip0.t-ipconnect.de] has left #navit ["und tschuess"]
14:50 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
14:50 -!- mode/#navit [+v xenos1984] by ChanServ
15:18 #navit: <@KaZeR> hi there
15:18 #navit: <@KaZeR> naggety: yep
15:21 -!- aerostitch [~aerostitc@c-67-164-55-119.hsd1.ca.comcast.net] has joined #navit
16:25 -!- ColdFyre [~lenny@172.92.43.110] has joined #navit
16:48 -!- jandegr [d5db90b7@gateway/web/freenode/ip.213.219.144.183] has joined #navit
17:23 #navit: <@KaZeR> hi jandegr 
17:23 #navit: < jandegr> ah hi kazer
17:27 #navit: < jandegr> this is where it is pulling kazer (disregard the actual reported issues for now)
17:27 #navit: < jandegr> https://7855-30791823-gh.circle-artifacts.com/0/reports/lint-results.html
17:28 #navit: < jandegr> and then this will be set to true https://github.com/navit-gps/navit/blob/Gradle_lint/navit/android/build.gradle#L31
17:29 #navit: < jandegr> and done with inserting new ones :)
17:33 #navit: < jandegr> if an error dected, CI fails on the test and no merging, at least if direct commit to trunk is disabled
17:34 #navit: < jandegr> https://circleci.com/gh/navit-gps/navit/7760?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
17:36 #navit: < jandegr> [WIP] I already have checkstyle working on CI to check the coding style but still have difficulty to upload the report to the artefacts
17:41 #navit: <@KaZeR> jandegr: nice
17:42 #navit: <@KaZeR> i'll review this in details in a bit
19:01 #navit: < aerostitch> @all please fill https://goo.gl/forms/eQ5FY18Fj5LwEscE2 to help the choice of the navit coding style
19:09 -!- jandegr [d5db90b7@gateway/web/freenode/ip.213.219.144.183] has quit [Ping timeout: 260 seconds]
20:03 -!- ilovekiruna [~ilovekiru@2a02:8108:d00:110:d96c:93f4:8be1:474b] has joined #navit
20:03 -!- mode/#navit [+v ilovekiruna] by ChanServ
20:14 #navit: <+ilovekiruna> hi all
21:24 #navit: <@KaZeR> hey ilovekiruna 
21:25 #navit: <@KaZeR> aerostitch: a google form will give you some teeth grinding :)
21:25 #navit: <+ilovekiruna> Hey KaZeR
21:28 #navit: < aerostitch> whatever, it seems whatever I do I will have some teeth grinding anyway, so...
21:28 #navit: < aerostitch> Trying to help, I cam help elsewhere if people are unhappy
21:46 #navit: <+ilovekiruna> KaZeR; sorry to ask again the same question
21:46 #navit: <+ilovekiruna> any idea how i can record my route tomorrow on the longer drive directly in navit?
21:46 #navit: <@KaZeR> ilovekiruna: keep asking, one day i might answer :)
21:47 #navit: <+ilovekiruna> ofc I could do it in another app
21:47 #navit: <@KaZeR> aerostitch: nah it's just that the bigger the team, the more different opinions you'll have!
21:48 #navit: <+ilovekiruna> want to record also if anything goes wrong in anvit
21:48 #navit: <+ilovekiruna> I just dont like that we dont have that easy logging on android, like on pc systems, if i remember correctly
21:51 #navit: <@KaZeR> well we do have the logs... not sure i follow you here
22:21 #navit: <+ilovekiruna> KaZeR: what i understood so far, is that I have to somehow extract it via 3rd party apps
22:21 #navit: <+ilovekiruna> or am i wrong?
22:21 #navit: <@KaZeR> what data are you trying to extract?
22:21 #navit: <+ilovekiruna> like log messages from navit
22:22 #navit: <@KaZeR> things like "debug:navit:transform:input coord 2: (1278617, 6126581)" ?
22:23 #navit: <+ilovekiruna> or am i wrong?ink so
22:23 #navit: <+ilovekiruna> I think so, u know for example to make sure if navit wants to turn me again where no road is ;-)
22:26 #navit: <@KaZeR> for routes, you can also dump the route via dbus, you'll get the segment info, expected duration, etc
22:27 #navit: <+ilovekiruna> on android?
22:29 #navit: <@KaZeR> i was talking about linux for that :)
22:29 #navit: <@KaZeR> oh wait
22:29 #navit: <@KaZeR> i missed one of your lines : any idea how i can record my route tomorrow on the longer drive directly in navit?   
22:29 #navit: <+ilovekiruna> on linux, i know such things are very simple
22:30 #navit: <@KaZeR> so you want to enable the gps log, right?
22:30 #navit: <+ilovekiruna> gps log and potentially also general logs, in case sth unexected shows up
22:30 #navit: <+ilovekiruna> that we could replay the log afterwards
22:31 #navit: <+ilovekiruna> following a recent discussion
22:32 #navit: <+ilovekiruna> was happy to learn today again how to use waypoints in NAVIT :D
22:42 #navit: <@KaZeR> well using the gps logs we should be able to reproduce any issue you might encounter..
22:42 #navit: <@KaZeR> yes, waypoint. very useful if you want to follow a specific route
22:44 #navit: <@KaZeR> waypoints might be poorly documented in the wiki...
22:44 #navit: <@KaZeR> hint, hint :)
23:14 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
23:33 -!- Horwitz [~mich1@p200300800E009800022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
23:46 -!- Horwitz [~mich1@p200300800E00AC00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:46 -!- mode/#navit [+o Horwitz] by ChanServ
--- Log closed Thu May 10 00:00:15 2018