igniterealtime / pade

Pàdé (Yoruba word for Meet) is a browser extension (Chrome/Edge) based unified communications desktop client for Openfire.
https://igniterealtime.github.io/pade/
Apache License 2.0
104 stars 46 forks source link

Losing messages #198

Closed robertokir closed 4 years ago

robertokir commented 5 years ago

In Pade 1.3.1 with Converse 5.0.1 I'm losing messages (PMs). Factory reset doesn't solve this. In other XMPP clients the messages are still available.

deleolajide commented 5 years ago

Thanks for posting this issue :-)

Could you please paste an image of your conversation the next time it happens in order for me to confirm (from the time-stamps) if the messages are missing from the chat history stored in the Openfire monitoring plugin DB.

I am currently debugging a similar issue, but in my case the messages were never saved in the DB.

marclaporte commented 5 years ago

What I see: I chat and all seems good. I click refresh, and most recent messages do not re-appear.

marclaporte commented 5 years ago

Video_2019-08-31_145444

robertokir commented 5 years ago

Screenshot Editor (3)

Timeago doesn't help identifying when this happened. But it was yesterday (Monday) morning, say about 10h? Where the arrow appears, there should be a message from me announcing the release of tiki 20.1 and recruiting volunteer testers, to which Rodrigo Lozada replied.

deleolajide commented 5 years ago

What I see: I chat and all seems good. I click refresh, and most recent messages do not re-appear.

We still have an outstanding one2one chat history issue with openfire. MAM2 support is only provided for MUC. See @guusdk comment in https://github.com/igniterealtime/openfire-monitoring-plugin/issues/5

deleolajide commented 5 years ago

Timeago doesn't help identifying when this happened. But it was yesterday (Monday) morning, say about 10h? Where the arrow appears

Thanks. This helps a lot :-)

deleolajide commented 5 years ago

image

Looks like the message never got saved. As Rodrigo responded, I can only assume the message got to the server. Looks like it is an issue with monitoring plugin. I think I will create an issue there and reference this for the attention of @guusdk

guusdk commented 5 years ago

Is there any kind of error in the logs around that time? I've previously seen a database error preventing a message from being stored in the archive.

deleolajide commented 4 years ago

I suspect this error was connected to the offline messaging issue on the server. I will reopen if it re-occurs