15:59:13 #startmeeting network-health 08/07/2023 15:59:13 Meeting started Mon Aug 7 15:59:13 2023 UTC. The chair is hiro. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:39 meeting pad: https://pad.riseup.net/p/tor-nethealthteam-2023-keep 16:01:19 does anyone has anything to discuss? 16:01:27 s/has/have 16:01:38 hmm, what week of gsoc are we?, let me check 16:01:48 my work has still things to b e done..of week 10 16:01:53 now we enter in week 11 16:02:02 ic 16:02:05 i suppose 16:02:13 yes 16:02:34 so, still 3 weeks 16:02:39 i guess it will be backlog for week 11..this week is going to be hectic for me..will have to finish all leftovers and required 16:03:08 btw hiro about the timing in the 16:03:10 collector 16:03:17 how is that handled? 16:03:23 yes, lasts weeks... to finish remaining stuff 16:03:41 @rishadbaniya[m] it just runs at midnight on the client 16:04:03 depending on the machine, load and client config it might take a few more minutes to process or less 16:04:58 collector.torproject.org has routines to fetch data from clients, if it finds an update it's published 16:05:11 the routines run every 60 minutes 16:05:24 if i fix my download of onionperf analysis at "op-xyz.net/analysiz.json.xz then, in the future what's the chance that the onionperf analysis files will be started to publish at /htdocs/analysiz.json.xz ..... 16:06:11 the path won't change 16:06:27 but if it does the code can be updated I guess 16:06:44 before it was publishing at htdocs and now it just publishes on the absolute url 16:06:46 on what case is the "/" moved to "/htdocs", just curious 16:06:59 is it availability of other logs 16:07:31 it was just an old config 16:08:10 sorry i've not check, hiro is the data you're parsing overlapping with the one rishadbaniya[m] is using? 16:08:26 or you both are using different files? 16:08:26 it could be 16:08:34 I am parsing onionperf files 16:08:39 the nalysis files for now 16:09:17 asking just to avoid duplicated work parsing... 16:09:18 i was parsing through one of my own custom struct implementing serde deserializer..i looked over the JSON schema(the appropriate version) 16:10:41 there's still work left ..so i might bring changes in that 16:11:00 rishadbaniya[m]: maybe the onionperf feature is big and you could divide it in several issues, like parsing the data being one of them, other analysing it, etc. 16:11:56 that way you can also push earlier the parser and we can help with it 16:12:06 @juga my problem though is not just parsing the data is also storing it in the DB 16:12:22 parsing with serde is quite straightforward 16:13:10 hiro: ic, then maybe your parser is not that useful for rishadbaniya[m] 16:13:12 no...it was my fault..for not managing time..there were many tech events this week at my university.was distracted too much..wasn't able to keep up the momentum..sorry for that..this is also the reason why the onionperf didn't finish in time..i'll cover up for that 16:13:30 i guess i can finish the onionperf feature 16:13:31 within time 16:14:02 sure.. i'll push the version 16:14:04 that i've completed 16:14:18 it's partially complete..might be helpful to improve too 16:14:19 :) 16:14:23 through feedbacks 16:14:45 rishadbaniya[m]: no worries, though we should probably start with other issue as latest next week 16:15:09 i'll keep the onionperf as backlog and finish the issues of Week 11 too 16:15:24 and finsih the backlogs by the end of week 11 16:15:52 as you see it goes with onionperf feature 16:16:38 Sure, i'll have it finished and week 11 stuffs too 16:16:51 ok, thanks 16:18:30 is everyone good? 16:18:32 * hiro is groot 16:18:42 from my side, nothing else, finishing with some "doing" issues this week 16:19:09 and i will end my backlogs left + Week 11 for sure 16:20:23 ok thanks everyone! 16:20:29 #endmeeting