The issue has been fixed in https://hg.prosody.im/0.10/rev/f755e0bdc60a
Thank you Matthew Wild ! On Thursday, October 29, 2015 at 1:18:08 PM UTC-5, pawel...@sip-communicator.org wrote: > > > > On Thursday, October 29, 2015 at 1:10:35 PM UTC-5, > pawel...@sip-communicator.org wrote: >> >> Hi, >> >> On Thursday, October 29, 2015 at 12:31:57 PM UTC-5, Thijs Alkemade wrote: >>> >>> Hi Pawel, >>> >>> You did not mention this, but from the log I’m concluding that the >>> <iq/>s are >>> routed through a MUC. Could it be that there are multiple instances of >>> the >>> same bare JID behind one nick in the MUC? I think there can some >>> unexpected >>> results when routing <iq/>s in Prosody when that happens (like a result >>> arriving in a different instance than the one which sent it). >>> >>> >> Normally it should not be the case, but we're going to investigate that >> further. >> > > It's strange that it's always this "result" packet getting lost and not > just some random packets. > > > -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To post to this group, send email to prosody-dev@googlegroups.com. Visit this group at http://groups.google.com/group/prosody-dev. For more options, visit https://groups.google.com/d/optout.
