element-web: Timeline corruption on develop - "Live timeline 0 is no longer live"
I’ve seen this ~3 times today, and Travis is getting bitten by it repeatedly.
Symptoms are stacktrace of:
Caught /sync error Error: live timeline 0 is no longer live - it has a neighbouring timeline
at Room../matrix-js-sdk/lib/models/room.js.Room.addLiveEvents (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:28527:19)
at SyncApi../matrix-js-sdk/lib/sync.js.SyncApi._processRoomEvents (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:35245:10)
at _callee9$ (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:34809:54)
at tryCatch (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:49866:40)
at Generator.invoke [as _invoke] (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:50100:22)
at Generator.prototype.(anonymous function) [as next] (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:49918:21)
From previous event:
at https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:34858:46
From previous event:
at SyncApi._callee10$ (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:34657:74)
at tryCatch (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:49866:40)
at Generator.invoke [as _invoke] (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:50100:22)
at Generator.prototype.(anonymous function) [as next] (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:49918:21)
From previous event:
at SyncApi._processSyncResponse (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:34946:22)
at SyncApi._callee7$ (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:34294:60)
at tryCatch (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:49866:40)
at Generator.invoke [as _invoke] (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:50100:22)
at Generator.prototype.(anonymous function) [as next] (https://riot.im/develop/bundles/c0b74508d5644578d135/bundle.js:49918:21)
consoleObj.(anonymous function) @ rageshake.js:61
16:44:19.277 rageshake.js:61
And a message you try to send gets stuck in localecho state at the bottom of the timeline (in practice it successfully sends).
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 30 (28 by maintainers)
Commits related to this issue
- Ask the user for debug logs when the timeline explodes Fixes https://github.com/vector-im/riot-web/issues/9260 Workaround for https://github.com/vector-im/riot-web/issues/8593 Requires https://github... — committed to matrix-org/matrix-react-sdk by turt2live 5 years ago
- Ask the user for debug logs when the timeline explodes Fixes https://github.com/vector-im/riot-web/issues/9260 Workaround for https://github.com/vector-im/riot-web/issues/8593 Requires https://github... — committed to matrix-org/matrix-react-sdk by turt2live 5 years ago
- Refuse splicing the live timeline into a broken position Credit to Matthew for basically solving this. Theoretically fixes spontaneous timeline corruption: https://github.com/vector-im/riot-web/issu... — committed to matrix-org/matrix-js-sdk by turt2live 5 years ago
- Refuse splicing the live timeline into a broken position Credit to Matthew for basically solving this. Theoretically fixes spontaneous timeline corruption: https://github.com/vector-im/riot-web/issu... — committed to matrix-org/matrix-js-sdk by turt2live 5 years ago
- Add a tiny bit of logging to work out what timelines are doing See https://github.com/vector-im/riot-web/issues/8593 — committed to matrix-org/matrix-js-sdk by turt2live 5 years ago
- Refuse to link live timelines into the forwards/backwards position See https://github.com/vector-im/riot-web/issues/8593#issuecomment-478681816 Previously (https://github.com/matrix-org/matrix-js-sd... — committed to matrix-org/matrix-js-sdk by turt2live 5 years ago
- Refuse to set forwards pagination token on live timeline Should fix the error seen in https://github.com/matrix-org/riot-web-rageshakes/issues/1389 (https://github.com/vector-im/riot-web/issues/8593) — committed to matrix-org/matrix-js-sdk by turt2live 5 years ago
- Refuse splicing the live timeline into a broken position Credit to Matthew for basically solving this. Theoretically fixes spontaneous timeline corruption: https://github.com/vector-im/riot-web/issu... — committed to matrix-org/matrix-js-sdk by turt2live 5 years ago
- Add a tiny bit of logging to work out what timelines are doing See https://github.com/vector-im/riot-web/issues/8593 — committed to matrix-org/matrix-js-sdk by turt2live 5 years ago
- Refuse to link live timelines into the forwards/backwards position See https://github.com/vector-im/riot-web/issues/8593#issuecomment-478681816 Previously (https://github.com/matrix-org/matrix-js-sd... — committed to matrix-org/matrix-js-sdk by turt2live 5 years ago
- Refuse to set forwards pagination token on live timeline Should fix the error seen in https://github.com/matrix-org/riot-web-rageshakes/issues/1389 (https://github.com/vector-im/riot-web/issues/8593) — committed to matrix-org/matrix-js-sdk by turt2live 5 years ago
- Remove timeline explosion rageshake prompt Concludes https://github.com/vector-im/riot-web/issues/8593 We are no longer seeing this error being triggered, and are considering it fixed. As a result, ... — committed to matrix-org/matrix-react-sdk by turt2live 5 years ago
Rageshake and reload button?