Sender | Message | Time |
---|---|---|
4 Feb 2025 | ||
* oh wait nvm, i'm seeing recommendations from other modules to define the pickel\_key using environmentFile | 22:32:41 | |
* oh wait nvm, i'm seeing recommendations from other modules to define the pickel_key using environmentFile | 22:33:03 | |
* i feel like it would be better if it automatically copied it over from the existing config though 🤔 | 22:33:08 | |
* i still feel like it would be better if it automatically copied it over from the existing config though 🤔 | 22:33:17 | |
* oh wait nvm, i'm seeing recommendations from other mautrix modules to define the pickel_key using environmentFile | 22:34:50 | |
I have the telegram bridge running with encryption and it works over restarts, I don't remember my config off the top of my head but it looks like you got it! | 22:54:21 | |
hmm not quite, i tried following the documentation for the telegram module, to try to match it up with the whatsapp one, and it doesn't seem to work. | 23:56:10 | |
i specifically tried to set MAUTRIX_WHATSAPP_ENCRYPTION_PICKLE_KEY= in the environmentFile , but that didn't seem to take. | 23:56:11 | |
* i specifically tried to set MAUTRIX_WHATSAPP_ENCRYPTION_PICKLE_KEY= in the environmentFile , but that didn't seem to take | 23:57:19 | |
5 Feb 2025 | ||
Redacted or Malformed Event | 00:06:29 | |
oh wait i think i got it | 00:06:46 | |
i just noticed that it uses envsubt unlike the telegram module | 00:06:57 | |
set, and that's it | 00:07:15 | |
i also had to set services.mautrix-whatsapp.settings.encryption.pickle_key = "$MAUTRIX_WHATSAPP_ENCRYPTION_PICKLE_KEY" | 00:07:35 | |
* I've got
set, and that's it | 00:07:36 | |
oh congrats then! | 00:07:57 | |
ok yeah, it just look like the whatapp bridge doesn't automatically pickup config from environment variables | 00:08:04 | |
* i just noticed that it uses envsubt unlike the telegram module | 00:08:20 | |
11 Feb 2025 | ||
I've gone ahead and removed myself from the matrix team and added myself as an explicit maintainer on Synapse. I also updated the tests related to matrix-synapse to reference the maintainers of the package itself as well. https://github.com/NixOS/nixpkgs/pull/381232 | 17:30:25 | |
12 Feb 2025 | ||
19:59:43 | ||
15 Feb 2025 | ||
10:19:28 | ||
10:43:21 | ||
26 Feb 2025 | ||
The
It appears that the async tests are not working properly. How was this not detected before, and does anyone know how Python packaging works well enough to go fix it? I've tried, but I couldn't figure out how to fix the issue. | 19:46:53 | |
2 Mar 2025 | ||
00:15:36 | ||
8 Mar 2025 | ||
what happened to pkgs.matrix-synapse-tools.rust-synapse-compress-state ? it seems to have disappeared from 24.11 | 08:25:10 | |
apologies, it was my fault given I merged the PR that did not only clean up a few synapse packages, but also renamed this attribute by accident | 08:26:25 | |
Try rust-synapse-state-compress for now, I filed a PR a few days ago that I'll merge in a minute | 08:27:10 | |
thanks | 08:27:26 | |
fixed now on 24.11 and master (the wrong alias is kept in aliases.nix to not break folks again who already updated) | 10:36:26 | |
apologies for the inconvenience! | 10:36:38 |