16:18:19 #startmeeting network-health 2024-04-29 16:18:19 Meeting started Mon Apr 29 16:18:19 2024 UTC. The chair is hiro. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:18:19 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:18:23 hey @matt[m] 16:18:23 thx 16:18:38 here is the usual pad https://pad.riseup.net/p/tor-nethealthteam-2023-keep 16:19:06 hiro: hey! any updates on the database side? :) 16:19:24 I did grant the role access to the tables last week already 16:19:29 is the error still present? 16:19:48 Let me check 16:21:50 Mmh, still getting 502 and permission denied from the APIs :/ I think I'll open a ticket for this, maybe it has to do with something that is not database-related 16:22:07 ook I'll check again permissions tto 16:22:32 @Geko, @juga do you also have a bank holiday on wed? 16:22:43 yep 16:22:47 * juga didn't realize 16:22:55 ah, oh, 1st May, yes 16:22:55 good! so we are all out on wed! 16:23:25 @juga I saw your ping on tor-dev 16:23:41 it's weird it is not being spotted in the tests... I wonder if something has not been applied to the DB 16:23:48 like some change 16:23:50 I'll check 16:23:54 ok, thanks 16:24:26 @ggus is it all good on your side? 16:24:59 @GeKo @ggus are you going to sort out the next meetup? 16:25:18 which one? 16:25:29 the relay meetup for may 16:25:32 or is it too early? 16:26:13 i can help gus, yes 16:26:34 not sure whether we alreaddy have a date from the last meetup 16:26:55 if not, i suspect we'll have the next one in june.. 16:27:00 ahhh I see 16:27:07 I thought we had one meetup each month 16:27:17 we try to do that, yes 16:27:24 yes, we have a date for the next meetup 16:27:29 may 13 16:27:40 i still need to send the meetup notes freom the last meeting 16:27:42 nice 16:27:58 like in 2 weeks, right :) 16:28:14 I am out on may 13 already... let me know if is there anything I can do to help 16:28:53 from the last meetup we had some question about how performances change between conflux and "no-conflux" and I was wondering if I should do some visualizations for that 16:29:05 ggus: i can be at that meeting and will brainstorm things as i go over my backlog this week 16:29:11 yes, plus we need someone from the network team 16:29:21 ahf: ^ 16:29:38 hiro: well we can point those folks to onionperf graphs 16:29:39 ? 16:29:41 on our website 16:29:50 i think they show what we have pretty nicely 16:30:03 there should be no need to create stuff ad-hoc imo 16:30:04 ahf: the next tor relay operator meetup will happen on May 13 at 19 utc 16:30:13 yeah but I have to admit those are a bit small.. I was wondering if it would help to do them a bit bigger 16:30:14 can we have someone from network team to help on the questions? 16:30:25 ggus: that's a monday? :o 16:30:40 it's after i am done with 1:1's so i can be there 16:30:55 oh sorry, may 11. 16:31:03 oh 16:31:06 the last one was on april 13. and i got confused. 16:31:20 i cannot do the 11th :/ 16:31:26 let me try to see if i can find somebody else to go on that day 16:32:29 hiro: i think the things we can see, like throughput changes should be visible on them 16:32:43 ahf: ok! 16:32:50 and wb GeKo o/ 16:32:51 ok then @GeKo one thing less to do 16:32:55 and the gap between used and adv bw we still have is visible as well 16:32:58 ggus: i'll get back to you on that 16:33:13 but i have not checked in details what we can get out of that change graphs-wise 16:33:21 ahf: thanks! 16:33:26 *detail 16:34:00 hiro: i wonder whether that's so mething we have created during sponsor61 actually 16:34:17 maybe there is a final report with graphs showing changes 16:34:32 mike and/or gaba might know about those... 16:34:39 if someone made a graph, I didn't 16:35:00 yeah, but mike might have collected sufficient ones we could re-use 16:35:07 yep 16:36:33 anyways if we are all good, we can end the meeting 16:37:33 * juga is good 16:37:38 * GeKo too 16:38:05 i'm good too 16:38:15 * matt is good 16:38:18 * hiro is groot too 16:38:21 ooook! 16:38:24 #endmeeting