fix #76 #77
fix #76 #77
Conversation
|
Travis insists that this does not compile. Does it? Your fix seems to be limited to the non-MUC archives. Does this problem need to be fixed in the MUC archives too? Would you be so kind at to add the issue that's fixed to the changelog? :) |
As far as I can tell, this issue is not being exhibited in the findMessages method of MucMamPersistenceManager. I have not looked into detail as to why. If it does later, I know where to find it :-)
I have this fix running on wikisuite.chat and using it everyday. I have no clue what is up with Travis, but I will check on any missing dependencies.
Sure thing |
Apparently it does not. Sorry about that. I have no clue on how the code got regressed. |
The last few commits were based on a branch, that got rebased upon the changes that were in igniterealtime#77 Somewhere along the line in my branch, variable names changed. This commit sets the record straight.
The last few commits were based on a branch, that got rebased upon the changes that were in #77 Somewhere along the line in my branch, variable names changed. This commit sets the record straight.
The last few commits were based on a branch, that got rebased upon the changes that were in igniterealtime#77 Somewhere along the line in my branch, variable names changed. This commit sets the record straight.
The last few commits were based on a branch, that got rebased upon the changes that were in igniterealtime#77 Somewhere along the line in my branch, variable names changed. This commit sets the record straight.
The last few commits were based on a branch, that got rebased upon the changes that were in igniterealtime#77 Somewhere along the line in my branch, variable names changed. This commit sets the record straight.
Monitoring plugin does not retrieve last page of chat history when is empty
This fix adds handling of xmppResultSet.isPagingBackwards() in findMessages()