-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
JSONDecodeError causes 500's while initial syncing or leaving room #6207
Comments
Here it is in all it's glory:
|
I upgraded to develop, and then ended up back on 1.4.0 (because of a VM issue) and it seems to have resolved itself. Presumably due to the database changes? |
makes sense. the issue might come up again though. |
I experienced a similar problem, I couldn't log in to my account on my homeserver because of a jsondecodeerror. After inspecting the database I found 846 events in the The only special thing I did was migrating from sqlite to postgres after upgrading to v1.5.0. I've checked the old sqlite database and it had no non-plain-text json columns ( I've solved the problem for now by removing the offending rows from the db ( edit: I've ran the migration script again as written above and some 846 jsons are not valid jsons again. Example row after migration (from postgres):
Row before migration (from sqlite):
|
Same problem here. Some users reported being unable to login. Deleting the offending rows solved the problem.
|
@richvdh Can this issue be re-opened or should a new one be created? |
Description
When trying to initial sync a clean device, or when trying to leave the room in question (HQ) I get a 500 error. I get what looks to be this everytime:
(Full traceback here: https://gist.github.com/Cadair/130ce1e704f2761415bdde17ef8d8482)
Version information
Version: 1.4.0
Install method: docker
The text was updated successfully, but these errors were encountered: