-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[Spaces] Handle and log when space summary requests time out instead of dumping a traceback #10026
Comments
Hmm, that error looks like its due to matrix.org server being overloaded. Does the request eventually succeed?
I don't think that would be related to that stack trace. |
Hard to tell. I suppose it does, since I can list the rooms of the space and join them. In that case it's probably as you say, with matrix.org being simply overloaded. Should maybe the error be clearer in the logs then? A stack trace can be frightening :).
OK, I'll open another issue for that other problem then. |
Agreed :) |
I think this is in general how all of our federation client code works (it doesn't handle timeouts well)? Not 100% sure on that though. |
It should just be a case of catching |
I think that This error is appearing from this line (specifically the synapse/synapse/federation/federation_client.py Lines 596 to 598 in c4cf0c0
This was added in #3638, not sure why we need the exception info here though? Probably to try to understand the cause of unknown (programming) errors? |
Description
I am hosting my own homeserver, while a colleague of mine is using matrix.org's server.
Yesterday, I have accepted an invite to join a Space sent by this colleague. This sort-of worked, but Element told me that Spaces were not enabled on my homeserver. I went and added
experimental_features: { spaces_enabled: true }
to my synapse, restarted, and the message was gone.However, I then found out the following errors in my homeserver's logs:
At the same time I realized that while the list of rooms of the space is shown correctly, the list of members of the space only shows my account, and not the account of my colleague who created the space. Not sure this is related though.
Steps to reproduce
Version information
If not matrix.org:
Version: v1.34.0
Install method: docker image
The text was updated successfully, but these errors were encountered: