-
Notifications
You must be signed in to change notification settings - Fork 85
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
Failed serial commands do not get dequeued. #789
Comments
What did you do to trigger the |
Hammered the server. It's running lots of sessions (40) each placing blocks at just under the spam limit (no actual /place, or other, commands though). Then the server saves the level, I think. Which causes all commands on all sessions to error in this way. It also doesn't seem to recover unless every session logs out. Unfortunately I haven't been able to repeat it on a server I own, despite clobbering them both less and so much the the kernel kills them off. |
Well, I've found something that kinda looks the same, except the server usually dies completely rather soon after.
|
If a command fails with the
Command Failed
message ... https://github.com/UnknownShadow200/MCGalaxy/blob/7bd2ad38ea3269c36f9e00d648cb2ef4476cde91/MCGalaxy/Player/Player.Handlers.cs#L528And this command went through the
ExecuteSerialCommands
function ...https://github.com/UnknownShadow200/MCGalaxy/blob/7bd2ad38ea3269c36f9e00d648cb2ef4476cde91/MCGalaxy/Player/Player.Handlers.cs#L701
The command will not get
Dequeue
'd ...https://github.com/UnknownShadow200/MCGalaxy/blob/7bd2ad38ea3269c36f9e00d648cb2ef4476cde91/MCGalaxy/Player/Player.Handlers.cs#L715
Because that is skipped and not run by the exception handler.
It will remain in on the queue and may get rerun when it's not wanted.
The text was updated successfully, but these errors were encountered: