!vxTmkuJzhGPsMdkAOc:transformierende-gesellschaft.org

NixOS Matrix Subsystem

129 Members
Coordination and discussion about the matrix subsystem in NixOS - https://nixos.wiki/wiki/Matrix63 Servers

Load older messages

SenderMessageTime
18 Sep 2023
@dandellion:dodsorf.asDandellionit'd be additive in any case really18:04:04
@hexa:lossy.networkhexa Oh yeah, that should work for most cases, except for enable_media_repo = false or send_federation = false 18:04:43
@hexa:lossy.networkhexaalso stream writers are a bit more complex with the different types they can be configured to handle18:05:58
@dandellion:dodsorf.asDandellionstream writers are problematic yep18:06:17
@dandellion:dodsorf.asDandellionor, at least, slightly annoying18:06:31
@hexa:lossy.networkhexaevents can be striped across multiple workers, most other things (typing, to_device, account_data, receipts, presence) cannot18:07:06
@hexa:lossy.networkhexasynapse will fail to boot when you configure a list where it expects a string, ask me how I know18:07:55
@hexa:lossy.networkhexa * synapse will fail to boot when you configure a list of workers where it expects a just a single one, ask me how I know18:08:13
@dandellion:dodsorf.asDandellionthat's right, it's also why my module only supports event persisters for now18:09:00
@ma27:nicht-so.sexyma27
In reply to @hexa:lossy.network
synapse will fail to boot when you configure a list of workers where it expects a just a single one, ask me how I know
oh, you too :D 		18:09:04
@ma27:nicht-so.sexyma27currently on the phone, will respond later18:09:16
@dandellion:dodsorf.asDandellionsince abstracting the other stream writers required a little more work at the time18:09:33
@dandellion:dodsorf.asDandellion * since abstracting the other stream writers properly required a little more work at the time18:09:45
@hexa:lossy.networkhexaas the worker setup is very brittle, we should probably try to co-maintain most of the thing18:12:06
@hexa:lossy.networkhexa * as the worker setup is very brittle, we should probably try to co-maintain most of the code18:12:12
@hexa:lossy.networkhexa * as the worker setup is very brittle, we should probably try to co-maintain most of the code required for a productive worker setup18:12:43
@hexa:lossy.networkhexaand not let everyone come up with a weird downstream solution18:12:50
@hexa:lossy.networkhexa * and not let everyone come up with an even weirder downstream solution18:13:07
@f0x:pixie.townf0x
In reply to @hexa:lossy.network
and not let everyone come up with an even weirder downstream solution
ha ha sweats 		18:14:42
@hexa:lossy.networkhexaI was not looking at you, I swear!18:15:02
@dandellion:dodsorf.asDandellionI think maintaining the map and making opinionated types of workers is something that should be in nixpkgs. I'm not sure what you are arguing for18:16:31
@ma27:nicht-so.sexyma27
In reply to @dandellion:dodsorf.as

I think Ma27 seemed quite negative about this generally, But personally I think just putting the maps inside services.nginx.commonHttpConfig is more than adequate even without RFC-42 nginx (Which I think is basically impossible without introducing some kind of DAG system similar to home-manager)

But I'll be changing my module to match the nixpkgs implementation and work towards upstreaming the autoconfig stuff

so, in case of an rfc42 compliant nginx module I'd be all in favor. ANd now back to reality ;-)

I'm somewhat afraid that we'll come up with something that will be incomplete and if you need to change something, you'll need to touch the module rather quickly or need something else (which is an actual problem with the nextcloud module).

However, two things: first of all, after having played around with my synapse and messed up a few things while doing that (e.g. read receipts being broken because of an nginx misconfiguration) I think that mweinelt has a point here. Also, it's a purely opt-in thing, so it might not be that bad after all. That said, is the current module on your github in a reviewable state?

19:12:23
@hexa:lossy.networkhexayeah, workers did in fact introduce subtle breakages for me as well, like crypto intermittently stopped working 😄19:53:16
@hexa:lossy.networkhexatraced that back to the stream writers, and disabled all but events as well19:53:37
@hexa:lossy.networkhexanextcloud is arguably worse with how large the nginx config actually is, and that you need priorities for location blocks19:54:49
21 Sep 2023
@dedmunwalk:matrix.orgdedmunwalk joined the room.23:08:51
22 Sep 2023
@hexa:lossy.networkhexahttps://www.youtube.com/watch?v=wVl-jw_O_MQ12:00:45
@hexa:lossy.networkhexa 
â—‹ matrix-synapse-worker-client1.service - Synapse Matrix worker client1
     Loaded: loaded (/etc/systemd/system/matrix-synapse-worker-client1.service; enabled; preset: enabled)
     Active: inactive (dead)

Sep 22 20:04:46 ganymede systemd[1]: Dependency failed for Synapse Matrix worker client1.
20:13:08
@hexa:lossy.networkhexa * 
â—‹ matrix-synapse-worker-client1.service - Synapse Matrix worker client1
     Loaded: loaded (/etc/systemd/system/matrix-synapse-worker-client1.service; enabled; preset: enabled)
     Active: inactive (dead)

Sep 22 20:04:46 ganymede systemd[1]: Dependency failed for Synapse Matrix worker client1.
Sep 22 20:04:46 ganymede systemd[1]: matrix-synapse-worker-client1.service: Job matrix-synapse-worker-client1.service/start failed with result 'dependency'.
20:13:27
@hexa:lossy.networkhexaworkers didn't start up after reboot20:13:37

Show newer messages

Back to Room ListRoom Version: 4