15:59:57 #startmeeting tor anti-censorship meeting 15:59:57 here is our meeting pad: https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469 15:59:57 editable link available on request 15:59:57 Meeting started Thu May 15 15:59:57 2025 UTC. The chair is shelikhoo. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:57 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:02 hi~hi~ 16:01:05 hi 16:01:37 hello 16:01:38 hello! 16:03:06 I will wait a few minutes for discussion topics. If there is anything you would like to discuss please add them now 16:04:36 Please send anything if there is someone we would like to discuss in this meeting 16:04:47 Please send anything if there is something we would like to discuss in this meeting 16:05:08 sorry for typo... 16:05:09 i have a follow up question from last week about testing the unreliable transport mode for snowflake 16:05:14 yes 16:05:19 please go ahead 16:05:35 would you like to do an open testing call to get more people trying it? 16:06:13 Yes, I think that is a reasonable thing to do after we finished our internal testing 16:06:19 okay great 16:06:34 i only just got around to looking at it this morning, sorry it took me so long to get to it 16:07:07 yeah, sorry for sending too many things to your review queue... 16:07:33 oh no worries :) there's always a bit of a backlog when people are away 16:07:45 hahaha yes... 16:07:53 that's it from it, i'll give some feedback on the documentation for the testing process in that case as well 16:08:17 it's a nice setup 16:09:08 hahaha... thanks!!! 16:09:14 I want to look into it at some point, I've never touched k3s or kubernetes before, I'm curious to learn a bit about it 16:09:47 and thanks cohosh for looking at the complex setup... It will take some learning to understand... 16:10:40 yeah i won't say i fully understand it yet 16:11:26 is the testing setup meant to faciliate review? why add a step that requires additional complex learning? 16:11:44 is the testing setup supposed to be reusable beyond testing the UDP-like transport branch? 16:11:56 yeah, it is 16:12:07 it is a system to automate the process to setup a staging environment for snowflake 16:12:15 from my undderstanding deploying something to the staging environemnt is hopefully not too complex 16:12:16 and is fully reusable 16:12:38 so i don't think peopl eneed to understand it to use it either as developers or as testers 16:12:58 but shelikhoo wanted some feedback on the set up 16:13:07 (let me know if i misunderstood) 16:13:21 deploying new branches don't requires understanding it 16:13:40 but making changes to the staging environment does 16:14:13 in a typical workflow, just replace a few string would be enough 16:14:15 the idea is that it will automatically deploy for branches/MRs, isn't it? 16:14:30 so it will be integrated in the snwoflake gitlab's repo 16:14:43 or is something you just enable for specific branches you want to test? 16:15:31 I have not made the changes to automated deploy for MR or branches, but that is possible 16:15:55 I think that would be too complex to be honest 16:16:21 right now it takes a few commit to the snowflake staging environment repo to build the container images 16:16:43 which could be automated and integrated to snowflake repo directly 16:17:17 and then, just replace container image url in the terraform file and then run a command to deploy it 16:17:21 maybe we don't want to pollute the snowflake repo, and this is only needed for certain branches 16:17:58 yes... I think we can keep it separate for the time being 16:18:07 sounds good to me 16:19:44 yes... but it is just a replacement for spending a few hours to setup a snowflake broker and snowflake server each time we wants to test a snowflake merge request 16:20:22 and shouldn't, on it self, create too much burden for maintenance 16:20:23 over 16:21:14 anything else we would like to discuss in this meeting? 16:21:25 not from me 16:22:13 okay 16:22:14 #endmeeting