You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure what might be causing this. It doesn't seem to happen often, but it definitely happened once; the last person left, and the icon remained there. There must be some kind of race condition, or perhaps some case in which the bot fails to recognize "itself" and thinks that the room is still occupied because the bot is in it.
The text was updated successfully, but these errors were encountered:
A) The bug is fixed when you bridge and re-bridge the room in question. That means that the error is probably related to the bridging or presence state, not to the Discord channel name cache or anything that discord.js or the Discord API is doing.
B) However, if you do !hubs users in the affected room, it shows that the presence state accurately represents nobody in the room. (Except the bot, which it is accurately filtering out.) This is almost identical to what it does to determine whether to put the orange diamond there.
C) This leaves a very small surface area to contain the bug. Some kind of race condition that I have failed to imagine is likely.
For now, I disabled the check against the current discord.js-cached channel name, making the room for errors even smaller, if the bug persists.
Not sure what might be causing this. It doesn't seem to happen often, but it definitely happened once; the last person left, and the icon remained there. There must be some kind of race condition, or perhaps some case in which the bot fails to recognize "itself" and thinks that the room is still occupied because the bot is in it.
The text was updated successfully, but these errors were encountered: