-
Notifications
You must be signed in to change notification settings - Fork 722
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
WebHost: fix AutoLauncher restarting rooms due to race condition #3333
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hard to make sure this works on live webhost, but the +5 should be fine and locker import is dead in customserver.
Co-authored-by: black-sliver <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another thing I just realized is that rooms_shutting_down.put(room_id)
won't run if there is an exception during shutdown (re-raise or in finally). So the room(s) then gets stuck, Maybe move rooms_shutting_down to finally and wrap the db_session in the finally block in a try-except-log?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be fine? Everything I could think of was addressed. Maybe test the final incarnation before pushing live?
(cherry picked from commit 663b50b)
What is this fixing or adding?
Rooms are spinning too much
How was this tested?
locally
If this makes graphical changes, please attach screenshots.