02:16:01 <babz> did anyone notice a regression with i915 in 14.2 ?
02:16:01 <babz> now my laptop freezes when I switch back from X to a tty
05:19:26 <luke_jobless_sb> 14.2 is out!
05:20:06 <SponiX> NICE
05:21:22 <SponiX> hmm, isn't showing up for me on the homepage
05:21:31 <SponiX> luke_jobless_sb: you got insider information?
05:35:31 <luke_jobless_sb> SponiX: it's for AWS subscribers for FreeBSD
05:35:46 <luke_jobless_sb> SponiX: who runs bsd
05:36:15 <luke_jobless_sb> hmm what's gonna break this time
05:36:20 <luke_jobless_sb> exciting
05:37:31 <SponiX> bectl is your friend
06:35:49 <HER> luke_jobless_sb: oh cool https://download.freebsd.org/releases/amd64/amd64/ISO-IMAGES/14.2/
06:42:44 <SponiX> HER: thanks for the link
06:56:26 <SponiX> https://termbin.com/926s   can anyone review my pf.conf and tell me what I'm doing wrong? the 1024 and above, and 65532 stuff doesn't seem to work properly
08:13:46 <TurtleCrazy> SponiX: `keep state` is set by default for all filter rules. Set it alone has no meaning IMHO
08:16:36 <TurtleCrazy> Statefull tracking options should follow this keyword : `... keep state (max 100, source-track rule, max-src-nodes 75,max-src-states 3, tcp.established 60, tcp.closing 5)
08:17:44 <SponiX> TurtleCrazy: thanks
08:18:33 <TurtleCrazy> SponiX: the correct syntax is `from $if to $if`: `from any to any`. The destination interface is missing
08:19:06 <SponiX> https://termbin.com/u747  is my current ruleset that seems to be doing what I need
08:19:22 <TurtleCrazy> `pass proto { tcp udp } from any to any port > 1024`
14:53:51 <ibs> Any tips for epub readers? I use Foliate now, which is great except it very buggy on FreeBSD it seems.
15:40:00 <polarian> dch: how is the freebsd native CI/CD going? (wasn't sure the best channel to ping you in to ask, but you speak a lot here so I thought here would be best :P)
15:41:15 <dch> its been on hold til december which is painfully close now. I have been chomping away at work stuff, and hope to do a glorious burst of activity over the winter to have something usable.
15:41:44 <dch> polarian: the main thing is I need to re-think the agent<>server protocol a bit after the initial implementation
15:42:04 <dch> originally it was a super simple line protocol, which is great for embedded systems
15:42:12 <dch> but not smart enough for the other systems
15:42:46 <dch> I did a hack which I'm not pleased with, where the line protocol had a JSON body appended to it
15:42:54 <dch> it worked, but it annoys me too much
15:43:29 <dch> luke_jobless_sb: 14.2-RELEASE is not out until the official releng email with pgp adornments comes out
15:44:12 <dch> IIRC there have been situations previously where the bits on mirrors were yanked prior to the email
15:44:34 <polarian> dch: haha, seems like you ended up doing what you wanted to avoid, homebrewing a new protocol
15:45:03 <dch> polarian: its a small JSON blob in the end. but many people asked if this could be a generic task runner
15:45:17 <dch> and to support that I need something a bit more sophisticated than plain lines
15:45:48 <polarian> sounds like a major rewrite is needed :/
15:45:52 <dch> for example in the json body you can have arbitrary data and a signature, for the client to decrypt, or for the server to store
15:45:54 <dch> not really
15:46:05 <dch> instead of this:
15:46:06 <polarian> well the entire communication protocol needs to be replaced no?
15:46:20 <dch> RESP: {"data": "whatever"}
15:46:45 <dch> I now need `{"cmd": "RESP", "data": "whatever"}`
15:47:06 <polarian> to be honest, it does seem a little pointless having a line protocol when you are using json already...
15:47:10 <polarian> you already need a json parser...
15:47:39 <polarian> so you are going to move all the commands from the line protocol into a single JSON query?
15:57:40 <dch> yep
15:57:53 <dch> commands and responses
15:58:20 <dch> it basically is curl + lua + ucl (which handles json for me)
15:58:27 <dch> so I'm ok with that as dependencies
15:59:11 <dch> curl for the websockets and storing artefacts
16:01:13 <voy4g3r2> how is this different than say a MQTT broker?
16:01:26 <voy4g3r2> just sending message around for consumption, execution and results
16:01:41 <voy4g3r2> CI/CD is a scary beast.. it reminds me of the way perl works.. many ways to do the same thing :)
16:01:57 <voy4g3r2> https://adventofcode.com/ <--- getting my head wrapped around.. maybe i will use lua this year
16:25:30 <dch> voy4g3r2: not significantly different. my first version had a central rabbitmq.
16:25:49 <dch> one of the harder pieces is job scheduling, so you need some thing external for that
16:26:24 <dch> but once you start using websockets for the job output then you can remove a message queue from the system
16:40:34 <voy4g3r2> yeah.. message queues are just like.. i got a message, let me process and typically assumes.. order does NOT matter
18:11:40 <luke_jobless_sb> dch: it should be the precursor ... my misunderstanding