-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Truncated rageshake logs & possibly related UISIs #10951
Labels
Comments
dbkr
changed the title
Truncated rageshake logs
Truncated rageshake logs & possibly related UISIs
Sep 25, 2019
It looks like this is correlated with the device not being able to decrypt messages in encrypted rooms, and appears to be specific to Firefox. Presumably something something indexeddb. |
Apparently it is not just firefox |
dbkr
added a commit
to matrix-org/matrix-react-sdk
that referenced
this issue
Sep 26, 2019
We left out later parts if we exceeded the maximum log size, which was deeply unhelpful since the problem almost certainly happened just before the user hit the 'submit debug logs' button. Instead, iterate backwards through the fragments and prepend them, leaving off the earlier ones if we run over the size. Also, check we're not going to run over the size before adding the fragment so we might actually stick to the maximum log size. May fix element-hq/element-web#10951
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Riot seems to have started truncating rageshake logs at some point, in some cases: symptoms being that the last entry in the rageshake log will be from a day or more ago from when the rageshake was sent. Usually the last line is it logging that it's sending a rageshake which is also absent, so I don't think it's just mismatched clocks.
The text was updated successfully, but these errors were encountered: