--- Log opened Wed Sep 27 00:00:59 2017
03:11 -!- noradtux [~noradtux@port-54865.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds]
03:24 -!- noradtux [~noradtux@port-24154.pppoe.wtnet.de] has joined #navit
03:42 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
04:23 -!- xenos19841 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
04:23 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Disconnected by services]
04:24 -!- xenos19841 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Client Quit]
04:32 -!- noradtux [~noradtux@port-24154.pppoe.wtnet.de] has quit [Ping timeout: 260 seconds]
04:32 -!- noradtux [~noradtux@2a02:2028:647:6601:ec4:7aff:fe33:3dc1] has joined #navit
06:20 #navit: < jkoan> Kazer: For my pull request #309 pini answered me by mail, he's saying that the cpack thing would not help him because debian wants source packages which cpack can't build. Even though the question is if we want to merge this pr to build for example Deb RPM an so on for us. It could be helpful
06:21 #navit: < jkoan> If you think it's a good idea, I will check out the branch again and fix the conflicts
06:39 -!- naggety [512f392b@gateway/web/freenode/ip.81.47.57.43] has joined #navit
06:45 #navit: < jkoan> Hi naggety
06:45 #navit: < jkoan> What's up today? :)
06:50 -!- ilovekiruna [~ilovekiru@ip2505a0ef.dynamic.kabel-deutschland.de] has quit [Quit: Konversation terminated!]
06:53 #navit: < naggety> Hi!
06:54 #navit: < naggety> Well, I think I need another coffee
06:54 #navit: < naggety> xD
06:57 #navit: < naggety> I've seen you have been working a lot
06:58 #navit: < jkoan> ? Why?
06:59 #navit: < naggety> With TMC and documentation
07:03 #navit: < jkoan> For tmc you mean the firmware for arduino and the Si4703?
07:08 #navit: < naggety> yes
07:11 #navit: < naggety> Can you help me a bit? In my PR (#314) they told me yesterday to solve some indentation issues. Can you tell me what issues are those?
07:11 #navit: < naggety> https://github.com/navit-gps/navit/pull/314
07:18 #navit: < jkoan> Tabs versus spaces in our project 8 spaces are one tab
07:22 #navit: < naggety> I used 8 spaces tabs
07:22 #navit: < naggety> As it's said in programm guidelines
07:32 #navit: < naggety> The indentation character must be a tab, right?
07:33 #navit: < jkoan> Check the lines KaZeR commited ;)
07:33 #navit: < naggety> what lines?
07:34 #navit: < naggety> Coding Style      Intention with tabs     8 characters per tab     K&R style     Function name at line start
07:34 #navit: < naggety> those ones? are from the wiki
07:35 #navit: < jkoan> Line 478, 486 in file and 494 in wince
07:35 #navit: < jkoan> Yes
07:37 #navit: < naggety> I don't see what is the problem with those lines. In fact, I changed them to correct indentation, because I thought they were wrong.
07:38 #navit: < naggety> For sure this is very easy, but this is my first contribution....
07:38 #navit: < jkoan> Using tab or spaces?
07:38 #navit: < naggety> sorry! I'm new!  xD
07:38 #navit: < naggety> tab
07:39 #navit: < jkoan> You don't want to see my first contribution xD
07:40 #navit: < naggety> At least I think they're tabs, I configured Eclipse to use tabs
07:44 #navit: < jkoan> That's strange... If I look into your repo directly everything seems fine
07:45 #navit: < youte> hi all
07:47 #navit: < jkoan> Hi youte
07:47 #navit: < youte> what's up
07:47 #navit: < jkoan> Naggety I added a review
07:48 #navit: < naggety> OK, thanks
07:48 #navit: < naggety> I was looking and looking and I didn't see what's wrong. Let's see what they say.
07:48 #navit: < naggety> hi youte
07:49 #navit: < youte> hi naggety
08:03 #navit: < naggety> jkoan: just to learn how I had to do it. If I had to make changes to my PR, how should I do? Just making another commit to the same branch?
08:06 #navit: < jkoan> Yes
08:06 #navit: < jkoan> Because of that you should work in branches in the future ;)
08:55 #navit: < naggety> you mean one branch per new feature, for example?
09:27 #navit: < jkoan> Yep
09:33 -!- noradtux [~noradtux@2a02:2028:647:6601:ec4:7aff:fe33:3dc1] has quit [Quit: Bye]
09:35 -!- noradtux [~noradtux@port-24154.pppoe.wtnet.de] has joined #navit
11:33 #navit: < naggety> As kazer said, I have just added to the wiki what I learned yesterday. Basically is the usage of the command gui.set()
11:33 #navit: < naggety> https://wiki.navit-project.org/index.php/OSD#GUI_commands
11:41 -!- naggety [512f392b@gateway/web/freenode/ip.81.47.57.43] has quit [Quit: Page closed]
14:32 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
14:34 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Read error: No route to host]
15:02 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
15:15 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Read error: Connection reset by peer]
15:46 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
15:50 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Read error: No route to host]
15:59 -!- pmckinley [~Peter_McK@88-110-212-139.dynamic.dsl.as9105.com] has joined #navit
16:40 -!- youte [~youte@32.ip-37-187-37.eu] has quit [Remote host closed the connection]
16:42 #navit: <@KaZeR> hi there
16:42 -!- youte [~youte@32.ip-37-187-37.eu] has joined #navit
16:42 #navit: < youte> hi
16:44 #navit: < jkoan> Hi Kazer
16:44 #navit: < jkoan> Hi again youte
16:45 #navit: < jkoan> What's up today?
16:47 #navit: <@KaZeR> jkoan: yeah i think that the idea behind #309 is worth it
16:47 #navit: < jkoan> So what do you suggest?
16:48 #navit: <@KaZeR> hi youte and jkoan
16:48 #navit: < jkoan> Fixing the conflicts?
16:48 #navit: <@KaZeR> jkoan: i commented on naggety's PR mostly because the format was inconsistent. I think that he probably used tabs instead of spaces or something like that
16:49 #navit: < jkoan> Naggety fixed old format issues. look at his repo and compare it with the current code on navits, his code is well formatted
16:53 #navit: <@KaZeR> i'll double check thanks. the thing is that when looking at the PR it looks like he fixed it only for the lines that he touched. Fixing it for the whole function would be better in that case
16:58 #navit: <@KaZeR> i see it now. Merged!
17:08 #navit: < jkoan> Nice!
17:09 #navit: < jkoan> Kazer do you want to take a big helping task to support traffic management? It's about the plugin integration
17:12 #navit: < youte> hi kazer have you see my mp? lol
17:14 #navit: < jkoan> KaZeR: you can push to my navit fork? Lol
17:24 -!- ilovekiruna [~ilovekiru@ip2505a0ef.dynamic.kabel-deutschland.de] has joined #navit
17:28 #navit: <@KaZeR> youte: replied
17:28 #navit: < ilovekiruna> Hi KaZeR
17:28 #navit: <@KaZeR> jkoan: it's probably because it's a fork, so github might be hiding some branches trickery to make it happen :)
17:28 #navit: <@KaZeR> hey ilovekiruna !
17:29 #navit: < ilovekiruna> I will try to make an empty test case today
17:29 #navit: < ilovekiruna> i dont understand the whole aws process of testing completely yet
17:29 #navit: < jkoan> KaZeR: i can also give you access i think
17:32 #navit: <@KaZeR> ilovekiruna: thanks! Happy to help if needed. If at first we can get the tests to run by manually triggering them, automating the tests when we push code should not be difficult
17:33 #navit: < ilovekiruna> KaZeR: yes, I hope for sth really simple
17:33 #navit: < ilovekiruna> what is still confusing for me, is whether i also need to install appium inside the virtualenv i send u as zipfile for uploading
17:33 #navit: < ilovekiruna> but maybe i just need to search a bit more
17:40 #navit: <@KaZeR> yeah not sure either
18:15 #navit: < jkoan> KaZeR: now you should also have push access to my navit fork (just in case you need it some time)
18:22 #navit: <@KaZeR> thanks
18:55 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
20:09 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Read error: No route to host]
20:16 #navit: < ilovekiruna> KaZeR: where  can i give u the zip file?
20:16 #navit: < ilovekiruna> guess it wont work, but want to confirm
20:21 #navit: <@KaZeR> ilovekiruna: how big is it?
20:21 #navit: < ilovekiruna> 800k
20:22 #navit: <@KaZeR> oh! maybe we could start a wiki page and attach it there
20:24 #navit: < ilovekiruna> is the wiki.navit-project.org still without ssl?
20:24 #navit: < ilovekiruna> i mean without auto-forced
20:25 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
20:26 #navit: <@KaZeR> any connection to `http` should be redirected automatically to `https`
20:26 #navit: <@KaZeR> seems to work for me
20:27 #navit: < ilovekiruna> btw: cant upload to wiki :(
20:27 #navit: < ilovekiruna> it is a zip file, that file type isnt permitted
20:28 #navit: < ilovekiruna> 	
20:28 #navit: < ilovekiruna> Permitted file types: png, gif, jpg, jpeg, svg.
20:28 #navit: <@KaZeR> oh! let me change that
20:29 #navit: < ilovekiruna> i wonder if that is good
20:29 #navit: < ilovekiruna> maybe it would be better to make a github repo with it
20:29 #navit: <@KaZeR> works for me too
20:29 #navit: <@KaZeR> i enabled zip files. If you want to do otherwise i can disable it
20:30 #navit: < ilovekiruna> will do it now once, but in the coming days better as git
20:30 #navit: <@KaZeR> sounds good
20:30 #navit: < ilovekiruna> https://wiki.navit-project.org/images/2/29/Test_bundle.zip
20:34 #navit: <@KaZeR> thanks
20:38 #navit: <@KaZeR> "Tests skipped due to test package parsing error. Please check Parsing result for more details. " but then the Parsing result log is empty :/
20:38 #navit: <@KaZeR> which appium version did you use?
20:40 #navit: < ilovekiruna> not specified in my file
20:40 #navit: < ilovekiruna> my guess is that when building the bundle, sth went wrong and no test is really registered
20:40 #navit: <@KaZeR> the zip file was created by appium directly?
20:40 #navit: < ilovekiruna> nope
20:41 #navit: < ilovekiruna> it followed this manual by amazon
20:41 #navit: < ilovekiruna> https://docs.aws.amazon.com/devicefarm/latest/developerguide/test-types-android-appium-python.html
20:42 #navit: < ilovekiruna> i see one problem
20:42 #navit: < ilovekiruna> seems like in my virtualenv, I use python3
20:42 #navit: < ilovekiruna> not python2.7
20:43 #navit: <@KaZeR> ha, the logs showed up : https://pastebin.com/VSBrBUyM
20:47 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Read error: No route to host]
20:50 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has joined #navit
21:04 -!- xenos1984 [~xenos1984@12-109-157-37.dyn.estpak.ee] has quit [Read error: Connection reset by peer]
22:03 #navit: < ilovekiruna> KaZeR: wondering now if i still need to install appium locally
22:03 #navit: < ilovekiruna> what do you think?
22:24 #navit: <@KaZeR> good question, i don't really know
22:24 #navit: <@KaZeR> how did you build the test cases?
23:09 -!- Horwitz [~mich1@p200300800E717300022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
23:22 -!- Horwitz [~mich1@p200300800E0CF800022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
23:22 -!- mode/#navit [+o Horwitz] by ChanServ
--- Log closed Thu Sep 28 00:00:01 2017