-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raiden crashes when Matrix server is changed #3080
Comments
This sounds very similar to what this gitter user experienced |
I received matrix log files from KI-Decentralized. There are exceptions for the relevant times trying to federate with the Exchange Union server. I've created issues in raiden-transport to provide us better insight into the state of the servers:
Additionally we should improve the handling of such failures in the matrix transport in Raiden itself. |
Probably fixed by raiden-transport changes and #3180 on client side |
Shouldn't this be easy to test? I would rather have a test to say that this is fixed or not. |
|
We have changed a lot of the code this issue referenced. Closing. |
I mistakingly ran Raiden with production config and explicity passed a flag to use transport01.
Command:
When i removed the
--matrix-server
flag, Raiden crashed with the following error:This is due to the fact that Matrix transport was looking to join a room for a specific channel and the room did not exist on the selected production server as the channel's room was created on transport01.
It would have been nice if Raiden displays a meaningful error message and stop.
The text was updated successfully, but these errors were encountered: