16:01:09 #startmeeting network-health 09/27/2021 16:01:09 Meeting started Mon Sep 27 16:01:09 2021 UTC. The chair is GeKo. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:09 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:01:12 okay 16:01:15 let's start 16:01:21 http://kfahv6wfkbezjyg4r6mlhpmieydbebr5vkok5r34ya464gqz6c44bnyd.onion/p/tor-nethealthteam-2021.1-keep 16:01:27 o/ 16:01:44 is the pad, please add your items in case you have not done so 16:01:58 and mark those you want to talk about in bold 16:02:27 o/ 16:03:08 ggus: ping for you in case you are around 16:06:10 okay 16:06:14 let's start 16:06:43 i have one discussion item 16:07:00 ok 16:07:03 and if ggus still shows up i can chat a b it about the eol work i did so far 16:07:15 hiro: i guess we should amend the support article? 16:07:26 and maybe write a follow-up mail to tor-relays@? 16:07:46 given that operators started to show up on irc and wondered why the metrics port did not show them anything 16:07:46 o/ 16:07:51 hihi 16:07:55 yes I did a fix in the code too 16:08:02 i will need to leave in 20 minutes. 16:08:08 it was a null comparison that was probably causing the issue some people mentioned 16:08:23 ? 16:08:26 I was waiting to see if that happened again to make a new release 16:08:50 are we talking about the same thing? :) 16:09:14 nope, but I meant that could go in the follow up 16:09:19 :) 16:09:29 hah, okay :) 16:09:34 yeah, sounds good 16:09:44 would you mind picking all of that up? 16:10:02 that is support article update and tor-relays@ follow-up? 16:10:59 yes 16:11:08 sounds good I'll add that to my tasks 16:11:48 thanks 16:12:05 do we have anything else we should discuss around the overload topic? 16:12:16 I don't think so 16:13:47 okay 16:14:13 ggus: so, i cleaned up the eol policy or what could be our start 16:14:15 https://gitlab.torproject.org/tpo/network-health/team/-/wikis/Relay-EOL-policy 16:14:31 and i started to create a spreadsheet with eol relays that have contact info 16:14:45 in the first round that gave me ca. 390 relays 16:15:08 but that operated on yesterday's data i had in my bad-relays database 16:15:22 i am not too happy with that 16:15:42 so i'll do something differently tomorrow just fetching onionoo data 16:15:49 and generate the csv file out of that 16:16:04 ggus: should we keep that on in nextcloud? 16:16:11 yes, gimme access 16:16:25 i do, once i have the one i am happy with 16:16:26 GeKo: can you list all the tor relay versions that are EOL for me? 16:16:36 in a ticket 16:16:37 should be tomorrow 16:16:40 ack 16:17:13 yeah, i can add that to network-health#56 16:17:18 err 16:17:23 network-health/team#56 16:17:24 i want to use metabase+onionoo to fetch that list 16:18:04 you mean you want to create that spreadsheet yourself? 16:18:11 or what is the idea? 16:18:58 no no, i just want play around with metabase+onionoo to see if can be useful next time 16:19:05 aha 16:19:17 I can also give you a grafana dashboard 16:19:18 well, i'll use onionoo, so that's that 16:19:43 with a interactive table that you can use to search and filter 16:19:43 but i'll add to the ticket what i am checking this time 16:20:29 ggus: am wondering about a general template for the mails we send 16:20:35 i guess we should create one? 16:21:25 GeKo: yes, we can recycle your previous EOL email 16:21:37 aha, right, good call 16:21:41 i'll go over that 16:21:55 and then add what i still like to the wiki page 16:22:22 +1 wfm 16:22:27 for EOL bridges, i would like to add something about enabling OBFS4. 16:22:44 well 16:22:59 the problem with bridges right now is that we don't have the contact info 16:23:23 yeah, i was thinking to open a ticket and restart the discussion about bridges and contact-info 16:23:26 i guess we could put that ticket onto our roadmap if we think that's useful 16:23:47 what was the rationale behind removing the contact-info? 16:23:49 just use https://gitlab.torproject.org/tpo/network-health/metrics/collector/-/issues/20983? 16:24:13 GeKo: ty! 16:24:22 ok thanks GeKo reading that 16:24:57 the ticket and lnks there is all i know 16:25:25 i *think* the reasoning was erring on potential issues for bridge operators 16:25:41 however, to my knowledge those issues were never spelled out 16:26:10 okay, that's all i had on my plate to talk about 16:26:26 do we have anything else for this week? 16:26:57 i will submit a new project to Outreachy 16:27:02 about gamification 16:27:12 i will share the pad with you, GeKo 16:27:26 great, please do 16:27:54 i'd started reading some papers about that more or less recently 16:28:10 as i think this could be a really cool and useful thing to get going 16:28:16 so, exciting :) 16:29:42 I just wanted to mention I think I have digged out the issue with collector and will probably write a proposal to modify how we download descriptors from dirauths 16:29:57 aha! 16:30:01 nice 16:30:11 yeah spent some time with collector in debug mode during the weekend 16:30:14 i need to go. o/ 16:30:29 is that related to the bw gaps we see on metrics, too? 16:30:32 ggus: o/ 16:30:54 some dirauths are just interrupting the download or refusing the connection, so then collector tries another dirauth and that might not have the descriptors it asks... this much I have uderstood. 16:31:10 GeKo: I have to see how that graph is built on metrics-web side in the r-server code 16:31:26 okay. one bug at a time :) 16:31:36 more likely the r-server reads a csv and that csv has holes in it 16:32:03 so I guess metrics web reads the bandwidth data and decides not to publish it for that day... I am not sure because there is a check about missing data 16:33:17 k 16:33:24 we'll see i guess 16:33:42 alright, let's call the meeting then 16:33:49 great! talk later 16:33:51 have a nice week everyone o/ 16:33:53 #endmeeting