Closed timokoesters closed 2 years ago
I saw that something related to this was done here: https://github.com/matrix-org/sygnal/commit/80f1d4820f248730cff626974496c0960b0d010c But this still rejects the pushes.
There was some discussion around https://github.com/matrix-org/sygnal/pull/292#discussion_r779757254 about whether it should be ignored or rejected.
Note that I saw Conduit not working on the current matrix.org Sygnal instance, so #292 did not break it, it was already broken.
I saw that something related to this was done here: 80f1d48 But this still rejects the pushes.
Note that this change only changed sygnal's behaviour to return a 400 rather than a 500 in this situation.
As this isn't a recent regression, we're reluctant to add in workarounds that run the risk of becoming permanent. Sorry!
Looks like "default_payload": null
was coming from this code that got fixed: https://github.com/ruma/ruma/commit/932fe4fa38accee577d1ab09ad004fb68e84d1d9
Conduit sometimes sends pushes with "default_payload":null
Sygnal crashes like this:
I plan to avoid sending nulls with the next Conduit release, but it would help if you add a quick workaround to Sygnal and deploy it.