| 3 Feb 2025 |
|  pbsds changed their display name from pbsds (FOSDEM) to pbsds. | 16:25:27 |
| 4 Feb 2025 |
|  Kira joined the room. | 22:21:09 |
| Kira | is anyone using any bridges with encryption? - i recently setup mautrix-whatsapp, but it looks like it's wiping out the encryption key on each restart | 22:28:52 |
| Kira | i'm planning on submitting a fix, but it seems surprising to me if no one else has run into this before | 22:29:35 |
| Kira | oh wait nvm, i'm seeing recommendations from other modules to define the key using environmentFile | 22:31:10 |
| Kira | * oh wait nvm, i'm seeing recommendations from other modules to define the pickel_key using environmentFile | 22:32:03 |
| Kira | i feel like it would be ideal if it automatically copied it over from the existing config though 🤔 | 22:32:18 |
| Kira | * oh wait nvm, i'm seeing recommendations from other modules to define the pickel\_key using environmentFile | 22:32:41 |
| Kira | * oh wait nvm, i'm seeing recommendations from other modules to define the pickel_key using environmentFile | 22:33:03 |
| Kira | * i feel like it would be better if it automatically copied it over from the existing config though 🤔 | 22:33:08 |
| Kira | * i still feel like it would be better if it automatically copied it over from the existing config though 🤔 | 22:33:17 |
| Kira | * oh wait nvm, i'm seeing recommendations from other mautrix modules to define the pickel_key using environmentFile | 22:34:50 |
 miloignis | 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 |
| Kira | 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 |
| Kira | i specifically tried to set MAUTRIX_WHATSAPP_ENCRYPTION_PICKLE_KEY= in the environmentFile, but that didn't seem to take. | 23:56:11 |
| Kira | * 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 |
| miloignis | Redacted or Malformed Event | 00:06:29 |
| Kira | oh wait i think i got it | 00:06:46 |
| Kira | i just noticed that it uses envsubt unlike the telegram module | 00:06:57 |
| miloignis | MAUTRIX_TELEGRAM_APPSERVICE_AS_TOKEN
MAUTRIX_TELEGRAM_APPSERVICE_HS_TOKEN
MAUTRIX_TELEGRAM_TELEGRAM_API_ID
MAUTRIX_TELEGRAM_TELEGRAM_API_HASH
MAUTRIX_TELEGRAM_TELEGRAM_BOT_TOKEN
set, and that's it
| 00:07:15 |
| Kira | i also had to set services.mautrix-whatsapp.settings.encryption.pickle_key = "$MAUTRIX_WHATSAPP_ENCRYPTION_PICKLE_KEY" | 00:07:35 |
| miloignis | * I've got
MAUTRIX_TELEGRAM_APPSERVICE_AS_TOKEN
MAUTRIX_TELEGRAM_APPSERVICE_HS_TOKEN
MAUTRIX_TELEGRAM_TELEGRAM_API_ID
MAUTRIX_TELEGRAM_TELEGRAM_API_HASH
MAUTRIX_TELEGRAM_TELEGRAM_BOT_TOKEN
set, and that's it
| 00:07:36 |
| miloignis | oh congrats then! | 00:07:57 |
| Kira | ok yeah, it just look like the whatapp bridge doesn't automatically pickup config from environment variables | 00:08:04 |
| Kira | * i just noticed that it uses envsubt unlike the telegram module | 00:08:20 |
| 11 Feb 2025 |
 Sumner Evans | 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 |
| Kira changed their display name from kira to Kira. | 19:59:43 |
| 15 Feb 2025 |
|  BenjB83 joined the room. | 10:19:28 |
| BenjB83 changed their display name from BenjamÃn Buske to BenjB83. | 10:43:21 |
| 26 Feb 2025 |
| Sumner Evans | The pantalaimon build seems entirely broken due to some tests failing.
$ NIXPKGS_ALLOW_INSECURE=1 nix shell --impure '.#pantalaimon'
warning: ignoring the client-specified setting 'trusted-public-keys', because it is a restricted setting and you are not a trusted user
warning: ignoring the client-specified setting 'trusted-public-keys', because it is a restricted setting and you are not a trusted user
error: builder for '/nix/store/53f7n472hy99gsp83i040wbwf12pf190-pantalaimon-0.10.5.drv' failed with exit code 1;
last 25 log lines:
> /build/source/tests/pan_client_test.py:27
> =============================== warnings summary ===============================
> tests/proxy_test.py::TestClass::test_daemon_start
> tests/proxy_test.py::TestClass::test_pan_client_sync
> tests/proxy_test.py::TestClass::test_pan_client_keys_upload
> tests/proxy_test.py::TestClass::test_server_users_update
> tests/proxy_test.py::TestClass::tests_server_devices_update
> tests/store_test.py::TestClass::test_new_indexstore
> /nix/store/vl9d79x9b9qyrihimavaaz8g5yla16d2-python3.12-pytest-8.3.4/lib/python3.12/site-packages/_pytest/python.py:148: PytestUnhandledCoroutineWarning: async def functions are not natively supported and have been skipped.
> You need to install a suitable plugin for your async framework, for example:
> - anyio
> - pytest-asyncio
> - pytest-tornasync
> - pytest-trio
> - pytest-twisted
> warnings.warn(PytestUnhandledCoroutineWarning(msg.format(nodeid)))
>
> -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
> =========================== short test summary info ============================
> ERROR tests/pan_client_test.py::TestClass::test_login
> ERROR tests/pan_client_test.py::TestClass::test_start_loop
> ERROR tests/pan_client_test.py::TestClass::test_history_fetching_tasks
> ERROR tests/pan_client_test.py::TestClass::test_history_fetching_resume
> ERROR tests/pan_client_test.py::TestClass::test_room_key_on_client_sync_stream
> ============== 6 passed, 6 skipped, 6 warnings, 5 errors in 0.36s ==============
For full logs, run 'nix log /nix/store/53f7n472hy99gsp83i040wbwf12pf190-pantalaimon-0.10.5.drv'.
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 |
