-
-
Notifications
You must be signed in to change notification settings - Fork 678
createRoom with initial_state event to increase own power level fails ungracefully #1882
Comments
I guess that Dendrite is making the normal PL event then applying the events in |
The canonical way to do this is via |
I still see this error when using the signal bridge on dendrite |
I also have this error with the signal bridge on dendrite 0.4.1 in docker monolith I replaced my account by
|
Interesting, so it causes a cascading failure. The PL event is treated as invalid which means it gets dropped but then all subsequent events reference it in auth events which then fail with |
I have the same error. Is there a workaround for now please ? |
Yes, see my comment at mautrix/signal#106. |
I think this brought a cascading failure to the federation between our servers: @ArnoPoitt cannot see my encrypted messages anymore (whether DM or in an E2EE room).
server: synapse 1.42.0 |
This should be fixed as of 562d742, so both 0.8.0 and 0.8.1 should contain the fix. |
I had added the preview wildcard for the production render apps to dendrite CORS settings. They work now. (try: https://test-harmony-web-pr-1879.onrender.com/login) This PR does the same for the test environment. We're still hardcoding for now. Will do a cleanup overhaul where we move these to a CSV origins environment variable
Background information
go version
: 1.16.5Description
When creating a room, specifying an initial_state event that increases the creating user's power level causes an internal server error and a half configured room. This differs from Synapse which creates the room correctly and applies the new power level.
I tested this against two personal instances and dendrite.matrix.org.
Steps to reproduce
initial_state
set to e.g.Dendrite will respond with an internal server error rather than succeeding or giving a more useful error. It also only half configures the room (presumably stopping when the error occurs and not reverting the previous changes) rather than creating the room entirely and correctly or not creating the room at all.
Relevant section of log:
Note: I am new to Matrix and not totally sure what the correct behaviour is here, particularly because increasing a power level that defaults to 100 seems like a strange thing to do. The mautrix-signal bridge does this, however, and expects a correctly configured room.
The text was updated successfully, but these errors were encountered: