Skip to content
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

The lobby closes all the time #168

Open
RugerNey opened this issue Nov 18, 2023 · 4 comments
Open

The lobby closes all the time #168

RugerNey opened this issue Nov 18, 2023 · 4 comments

Comments

@RugerNey
Copy link

Some time after starting and creating the lobby, I get a message in the console "Detected a part event. Destroying the lobby...". What is the reason for this and how can I fix it?

@xayanide
Copy link
Contributor

xayanide commented Dec 4, 2023

The triggers could be:

  1. User initiated, you used the 'close' or 'close now' command from the cli, and the console output typically looks like this:
[INFO] lobby - Detected a part event. Destroying the lobby...
[INFO] cli - Readline closed.
[INFO] cli - IRC client disconnected.

there is no reason to keep an empty lobby if the user has already left the irc

  1. Internet connection issues, the IRC client connection is lost, immediately triggering the part event.

  2. Timed out, some IRC servers like to disconnect users who have been inactive for a certain period.

If the message only says 'Detected a part event. Destroying the lobby...' and nothing else after that, I will need more details about your actions leading up to that message.

In terms of fixing, I doubt that the issue is coming from osu-ahr, it might be something else, once again, can you reproduce this?

@RugerNey
Copy link
Author

image
This is a screenshot I was able to take. It feels like it's due to lack of people, but in the config file I have a whole day set to close the lobby in this case. And it only takes literally an hour or two for this error to come out, which is very strange

@matte-ek
Copy link

This is most likely Bancho closing the room due to inactivity.

@RugerNey
Copy link
Author

This is most likely Bancho closing the room due to inactivity.

What do you recommend to make it active at some points to get around that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants