Inconsistant history
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Clément assigned to @jbpasquier and unassigned @bleme
assigned to @jbpasquier and unassigned @bleme
By Jean-Baptiste on 2019-09-02T09:26:02 (imported from GitLab project)
- Clément added 1 deleted label
added 1 deleted label
- Developer
Looks like a chunk of history is missing, so failed MAM request or the request was never made. Is it easy to reproduce?
If so, can you grab debug logs from converse?
- Developer
A MAM query: https://xmpp.org/extensions/xep-0313.html#example-2
@MattJ : Thank you very much !
@jbpasquier : Is this enough info for you ?
By Alexandre on 2019-09-05T13:02:39 (imported from GitLab project)
- Clément unassigned @jbpasquier
unassigned @jbpasquier
By Alexandre on 2019-09-15T16:31:17 (imported from GitLab project)
- Clément changed time estimate to 2h
changed time estimate to 2h
By Alexandre on 2019-09-21T13:54:50 (imported from GitLab project)
- Clément assigned to @dele
assigned to @dele
By Alexandre on 2019-10-02T13:29:23 (imported from GitLab project)
- Developer
This is fixed in latest Converse 5.x. However, the reconciliation between stored chat history and fetched chat history can still fail sometimes. Forcing the chat history to be always fetched with setting clear_messages_on_reconnection can completely prevent this issue.