16:01:33 #startmeeting network-health 12/11/2023 16:01:33 Meeting started Mon Dec 11 16:01:33 2023 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:33 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:01:53 hiro: mattrighetti[m]: ^ 16:01:59 not sure if ggus is around 16:02:19 we our pad as usual at: https://pad.riseup.net/p/tor-nethealthteam-2023-keep 16:02:25 o/ 16:03:23 I am here sorry 16:03:26 mattrighetti[m]: i saw you filed those descriptorparser tickets today 16:03:29 got caught in some issue 16:03:32 thanks for that 16:03:34 np 16:03:51 mattrighetti[m]: are you blocked on them in any eay? 16:03:53 *way 16:04:04 GeKo: yep, I got some more coming actually 16:04:14 I have to review those yet... 16:04:35 Not actually blocked but the API atm is going to parse those as array of strings, if they're not then the api will return an emtpy array 16:04:59 I see 16:05:04 We should probably decide how to standardize that across all tables 16:05:23 yeah... I need to check if those fields come all from the same document 16:05:32 Well, if those are intended to be like that then I can edit my parsing logic ofc 16:06:18 yeah let me have a look at all of them 16:06:26 I have a draft MR with two new endpoints that should return weights_probability (guard, middle, exit fractions) and exit_addresses 16:06:36 \o/ yay thanks for that 16:06:41 indeed! 16:06:51 mattrighetti[m]: and just keep those things filing 16:06:57 fine with different tickets 16:07:10 yep it's allright 16:07:20 I'll follow up with some questions on the MR, I have some questions on weights_probability 16:07:35 ok sounds good 16:08:04 Also, it could be a good idea to understand how clients are using those APIs so that we can make them better and more useful 16:08:24 yeah 16:08:41 I thnk the demo was scheduled for this week allhands right? 16:08:47 i think that could be done with the help of the operator community as well 16:08:55 we could start asking people if they want to start testing 16:09:05 asking for help and feeedback on tor-relays@ 16:09:07 yeah 16:09:41 mattrighetti[m]: you could ask on that mailing list once you think we are ready for that feedback part 16:10:26 yeah I'll send an email to pavel and start drafting a quick presentation for the demo 16:10:46 yep was thinking the same, I'll try to finish the latest MR and then it could be useful to gather feedbacks 16:11:07 @GeKo I was wondering if we should setup a topic on the forum just for the api 16:11:19 hrm! 16:11:26 we could do that 16:11:49 i am not much of a forum person but maybe a bunch of relay operators are 16:12:02 once we open it up we could ask people to discuss there... 16:12:08 and the more different audiences we get the better 16:12:12 yeah, fine with me 16:12:20 yeah I think I have to reset someting in my account to have access again 16:12:24 mattrighetti[m]: sounds good! 16:12:41 yes thanks @mattrighetti[m] 16:13:16 Other than that the APIs look good, nothing more to add :) 16:13:25 nice 16:13:29 it does indeed! 16:14:12 hiro: would it be worth putting the probably final revision of tor_fusion on your plate for this week? 16:14:21 I think so 16:14:24 let me add that 16:14:27 that way you might be done with that part of network-health/team#315 16:14:43 and don't have to worry about s112 o3.5 for a while 16:14:49 ugh 16:14:58 wrong issue number? 16:14:58 #313 it was 16:15:03 :) 16:15:11 :) 16:15:16 hiro: thanks 16:16:18 okay. all the other stuff looks good to me 16:16:35 do we have any questions/concerns/topics to discuss? 16:16:42 (additional ones, that is) 16:16:46 * juga is good 16:17:40 okay, nobody raises their virtual hand 16:17:55 then we are good to go it seems \o/ 16:17:59 thanks everyone 16:18:02 #endmeeting