I'm noticing some strange behaviour deep inside synapse and wondering if anyone here has seen it before / is familiar with it.

Symptom: new 'space-visible' rooms are not showing up in /hierarchy
Reason: because get_rooms_that_allow_join is checking that the allow key is a list, and it's coming back as a tuple https://github.com/element-hq/synapse/blob/develop/synapse/handlers/event_auth.py#L329

-> Reason: when the room is created, the join_rules event calls check_event_allowed - https://github.com/element-hq/synapse/blob/develop/synapse/handlers/message.py#L1289 - which calls event.freeze() which seems to be changing lists to tuples - https://github.com/element-hq/synapse/blob/develop/synapse/module_api/callbacks/third_party_event_rules_callbacks.py#L294
--> so that when the event is being pulled from cache, the allow list is a tuple. But when I restart the server, it gets pulled from the DB and deserialized as a list.

I'm confused why I'm seeing this behaviour in my server, and why it's not a bigger problem across synapse

        if len(self._check_event_allowed_callbacks) == 0:
            return True, None

— https://github.com/element-hq/synapse/blob/develop/synapse/module_api/callbacks/third_party_event_rules_callbacks.py#L282C1-L283C30

this might be why it's not widely seen. However it is a very valid bug, well done for spotting it!

Olivier 'reivilibre':

access to the user ID of requester

"access to the user ID of the requester"

Remove support for PostgreSQL 11 and 12.

We should pull this one up to the top, so it's front and centre.

Add previously-undocumented last_seen_ts

"last_seen_ts query parameter ..."

Alpine Linux Synapse Package Maintainer within installation.md

"within the installation instructions"

nice-to-have: It'd be nice to link to the config documentation for each config option that's mentioned.

Hello everyone,

I wanted to ask about the use of the SYNAPSE_HTTP_PORT variable. From what I understand, based on the README inside the Docker folder, I should be able to generate the configuration using a port different from the default 8008. That is:

If I run the command:

docker run -it --rm
-v synapse-data:/data
--env-file .env.dev
-e SYNAPSE_SERVER_NAME=Juan
-e SYNAPSE_REPORT_STATS=no
-e SYNAPSE_HTTP_PORT=1234
synapse-dev generate

The configuration file should set the port to:

listeners:

• port: 1234
  tls: false

But it’s not working. Am I misunderstanding how I should implement this?

I misunderstood :)

eyes on the changelog for v1.122 please? https://github.com/element-hq/synapse/blob/release-v1.122/CHANGES.md