!vxTmkuJzhGPsMdkAOc:transformierende-gesellschaft.org

NixOS Matrix Subsystem

150 Members
Coordination and discussion about the matrix subsystem in NixOS - https://wiki.nixos.org/wiki/Matrix74 Servers

You have reached the beginning of time (for this room).

SenderMessageTime
18 Sep 2023
@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
@ma27:nicht-so.sexyma27
In reply to @hexa:lossy.network
â—‹ 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'.
seems as if they were marked as broken as a result of something they depend on. any chance you can find out what that is? 		20:15:41
@hexa:lossy.networkhexa 
# systemctl show -p Requires matrix-synapse-worker-client1
Requires=sysinit.target matrix-synapse.service -.mount "var-lib-matrix\\x2dsynapse.mount" system.slice
20:16:29
@hexa:lossy.networkhexafailure set talk to my OIDC provider L/20:18:44
@hexa:lossy.networkhexa * failure set talk to my OIDC provider 20:18:45

Show newer messages

Back to Room ListRoom Version: 4