tigase@muc.tigase.org kicks my clients if I use them both (#1418)

Unknown opened 4 years ago

Dino HEAD, Conversations 2.9.0+fcr, same account, same nick, different resources.

Log from Dino: https://gist.github.com/licaon-kter/5027b4fdb34144abc9e8deb537fabdf3 (you can't see the error in the UI since it just reconnects) Conversations logcat outputs the same 110 and 170 codes (you can see you are not joined since it does not reconnect)

No issue if I use only one client.

Unknown commented 4 years ago

[2020-11-17 17:03:19] <Wojtek>: @Licaon_Kter 110 - 'self presence', '170' - room is publicly logged; adding 170 in this case
[2020-11-17 17:04:25] <Wojtek>: it seems like a race condition (mostly something due to us using cluster and s2s connections having some delay when re-connecting)

Unknown commented 4 years ago

Any news?
Unknown commented 4 years ago

Unfortunately not. We do keep this on our to-do.

Does it happen that often?
Unknown commented 4 years ago

100% of the time

I had to disable bookmark sync to have at least Conversations joined in that group.

Once I join Dino I get disconnected.
Unknown commented 4 years ago

@licaon-kter does it happen only with Dino?
Unknown commented 4 years ago

I didn't test other combos, just Dino+Conversations.
Unknown commented 4 years ago

Could you try to reproduce it with other clients? Unfortunately I can't reproduce it nor run Dino (easily).

If you could also share packet id's from the most recent occurrence it would help
Unknown commented 4 years ago

I can repro with Converse.js and Profanity, same 110 and 170. Profanity closes the chat window.
Unknown commented 4 years ago

@licaon-kter could you try now on muc.tigase.org?
Unknown commented 4 years ago

Thanks
Login to comment

Type

Bug

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#1418