-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kind is undefined #80
Comments
Here is the stack trace from my instance:
|
Upon refresh it does load, but even though it shows invite_user joining, it still states "Waiting for operator to join" |
This should be fixed on main, feel free to reopen if you still have issues. |
That "Waiting for operator to join" is a feature. Change |
I get that it's a feature. But the invited user joined. And still the condition to hide that message wasn't met. What is the condition that needs to be satisfied? |
So if you have that feature turned on, your PL is set to a low enough value that you cannot send messages. The invited user must bump your PL up so that you can send messages. I see now that this isn't communicated clearly in the documentation. |
Describe the bug
When a new user tries to chat with me from my page, it seems that the registration on my homeserver is too slow and the user is greeted with an error. Reloading the page or pressing the chat button again corrects the problem. It seems like some race condition from the chat app while waiting for the user registration to complete.
To Reproduce
The first time a user visits my page and click the chat icon, the chat box will produce the following error:
In the console, I can see repeatated calls to the register endpoint of my server
Reloading the page OR pressing the chat button again will make chat work properly
Expected behavior
The chat window to load properly on first key press without any error.
Screenshots
Desktop (please complete the following information):
Additional context
Same behavior in different browsers and on different devices.
The text was updated successfully, but these errors were encountered: