13:02:47 #startmeeting Network Health 2026-09-14 13:02:47 Meeting started Mon Sep 14 13:02:47 2026 UTC. The chair is hiro. Information about MeetBot at https://wiki.debian.org/MeetBot. 13:02:47 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:03:05 #link https://pad.riseup.net/p/tor-nethealthteam-2026-keep 13:04:10 alright who wants to go first? 13:04:39 i can 13:05:05 i was mostly doing different bad-relay and n-h analyses last week 13:05:26 and debugging issues with missing data in our db 13:05:45 this week i plan to make actual progress on p183 and p203 work 13:05:57 in parallel to the ongoing analyses 13:06:00 that's all from me 13:06:15 on p183 especially is there something that I am blocking you on? like data you are missing or something else? 13:06:55 if we conclude we are done with O3 then there is nothing blocking me 13:07:19 because we tailored O4 to be the follow-up taking results from O3 into account 13:07:47 uhm yes, I'll give it a review before the sync on wednesday... and I'll ask what you think about that 13:07:53 i think we are actually done and can close O3 but we can discuss that part on wed 13:08:23 and then it's just a matter on thinking about where we want to put the stuff we do in O4 13:08:49 we could have that as part of the final report or put it on the anomaly part of the n-h wiki 13:08:55 or both 13:09:06 *of thinking 13:09:17 so yes we can chat about it on wed, but I'd say both 13:09:20 but that's something we can hammer out on wed as well 13:09:23 yeah 13:09:36 so, some decisions to be made but nothing really blocking i think 13:09:57 so if we had time it would be nice to have a sort of network-health published report or even a paper out ... but we should weight how much effort that would be 13:10:20 well that report is still outstanding 13:10:23 I mean not just for the final project report, but as a whitepaper kind of thing or even a paper that is published somewhere 13:10:24 and part of the project 13:10:43 yeah that's why I am saying that 13:11:09 we can discuss what we want to do on that front 13:11:11 I think that is very good so it could be published in a more formal way so people can cite it and all 13:11:21 there should be time for that until the project ends 13:11:29 at the end of the year 13:12:24 alright but yeah let's talk about that 13:12:46 sarthikg: do you want to go next? 13:12:54 yeah 13:14:09 i have added some remaining charts for the relays by ip-version counts, both or & exiting. apart from that, have been fixing a few layout stuff for mobile usability. 13:14:48 additionally, i'm running aggregator from 2020, it seems like the pipelines have run for a few days already, and we do have more data now 13:15:05 i have raised a few issues where they are getting stuck now. 13:16:06 mostly that, and aggregate screens for data. i'm still working on the chart-details screens, those have more complication than i expected for allowing for server-rendered images, etc. 13:16:23 some wiring is pending, but overall, that's almost done also 13:17:09 thanks sarthikg 13:18:12 on my side I have been working on the ansible to install the onionperfs, it was a bit outdated. Also on the data needed by sarthikg for the website and on filling up gaps in the database. I'll am running the backfiller on metricsdb-03 and it is a bit slow but catching up on the missing data. 13:18:22 I hope to have everything finished on this side this week. 13:18:32 and have the onionperfs start measuring 13:18:36 that's it. 13:20:07 alright I think @juga is still struggling with the power outage 13:20:18 if there isn't anything else we can end the meeting 13:20:24 * hiro is groot 13:20:48 I'm groot 13:21:25 hey Rohithh good to see you! o/ 13:21:43 i'm good 13:21:56 alright 13:21:59 #endmeeting