did anyone notice a regression with i915 in 14.2 ?

now my laptop freezes when I switch back from X to a tty

14.2 is out!

NICE

hmm, isn't showing up for me on the homepage

luke_jobless_sb: you got insider information?

SponiX: it's for AWS subscribers for FreeBSD

SponiX: who runs bsd

hmm what's gonna break this time

exciting

bectl is your friend

luke_jobless_sb: oh cool download.freebsd.org/releases/amd64/amd64/ISO-IMAGES/14.2

HER: thanks for the link

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

SponiX: `keep state` is set by default for all filter rules. Set it alone has no meaning IMHO

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)

TurtleCrazy: thanks

SponiX: the correct syntax is `from $if to $if`: `from any to any`. The destination interface is missing

termbin.com/u747 is my current ruleset that seems to be doing what I need

`pass proto { tcp udp } from any to any port > 1024`

Any tips for epub readers? I use Foliate now, which is great except it very buggy on FreeBSD it seems.

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)

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.

polarian: the main thing is I need to re-think the agent<>server protocol a bit after the initial implementation

originally it was a super simple line protocol, which is great for embedded systems

but not smart enough for the other systems

I did a hack which I'm not pleased with, where the line protocol had a JSON body appended to it

it worked, but it annoys me too much

luke_jobless_sb: 14.2-RELEASE is not out until the official releng email with pgp adornments comes out

IIRC there have been situations previously where the bits on mirrors were yanked prior to the email

dch: haha, seems like you ended up doing what you wanted to avoid, homebrewing a new protocol

polarian: its a small JSON blob in the end. but many people asked if this could be a generic task runner

and to support that I need something a bit more sophisticated than plain lines

sounds like a major rewrite is needed :/

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

not really

instead of this:

well the entire communication protocol needs to be replaced no?

RESP: {"data": "whatever"}

I now need `{"cmd": "RESP", "data": "whatever"}`

to be honest, it does seem a little pointless having a line protocol when you are using json already...

you already need a json parser...

so you are going to move all the commands from the line protocol into a single JSON query?

yep

commands and responses

it basically is curl + lua + ucl (which handles json for me)

so I'm ok with that as dependencies

curl for the websockets and storing artefacts

how is this different than say a MQTT broker?

just sending message around for consumption, execution and results

CI/CD is a scary beast.. it reminds me of the way perl works.. many ways to do the same thing :)

adventofcode.com <--- getting my head wrapped around.. maybe i will use lua this year

voy4g3r2: not significantly different. my first version had a central rabbitmq.

one of the harder pieces is job scheduling, so you need some thing external for that

but once you start using websockets for the job output then you can remove a message queue from the system

yeah.. message queues are just like.. i got a message, let me process and typically assumes.. order does NOT matter

dch: it should be the precursor ... my misunderstanding