This message was deleted.
# clouds
steep-balloon-41261
08/28/2023, 2:49 PMThis message was deleted.
d
dry-elephant-14928
08/28/2023, 3:46 PMHi @creamy-notebook-61404, you may have discovered a race condition! with 3, does it ever stop ?
c
creamy-notebook-61404
08/29/2023, 7:16 AMHi @dry-elephant-14928. It doesn't seem to stop (tested for at least 6 minutes).
1. When disconnecting, I await the room.disconnect().
2. I reconnect after I received the Disconnect event.
3. I reuse the same Room object (js-sdk)
4. I receive the ParticipantMetadataChanged every couple of milliseconds, so very fast. (maybe it's a js-sdk bug?)
d
dry-elephant-14928
08/29/2023, 7:42 AMthank you for these details. we'll take a look. It's quite possible the bug is in JS SDK
c
creamy-notebook-61404
08/29/2023, 10:52 AMYes probably, because I just tested my older code where I didn't reuse the Room object and there was no issue.
d
dry-elephant-14928
08/30/2023, 9:03 PMCC: @polite-kilobyte-67570, this seems to occur only when the same Room object is re-used across connections. Maybe we didn't remove a listener so both are racing?
p
polite-kilobyte-67570
09/04/2023, 1:45 PM@creamy-notebook-61404 sorry for the delay on this, I’ll look into what’s going on there this week!
polite-kilobyte-67570
09/06/2023, 11:56 AMHi Marteen,
I tried to reproduce this by passing disconnecting and re-connecting with a token of the same user identity but different metadata, but did not see the same behaviour.
Could you create a minimal example reproduction that showcases this behaviour so that we can further debug what’s going on? thanks!
polite-kilobyte-67570
09/13/2023, 8:47 AMThis should be fixed in
v1.13.3