-
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Unhandled packet assertion. Can this throw instead? #87
Comments
The packet that was unhandled is an This crash is a known bug in the packet handling logic, and has been addressed in the upcoming major revamp of MySQLNIO, as have all the other fatal errors, assertion failures, and other unnecessary crashes on failure. |
* Update package support files (dockerignore, readme, CI workflows) * Minimal code cleanup - replace `fatalError()`s and `assert()`s with thrown errors, add escapes in comments so Xcode's inline formatting doesn't choke, add `any` to existential usage, other very minor tweaks. * Fix the "server sends error packet when nothing else is going on causes crash" problem - fixes #87 * Add fix for the bad protocol version bug - fixes #91 * Fix the tests bug that causes problems with the `foos` table still existing when the integration tests for FluentMySQLDriver run. * Work around weird deadlock on Linux * Remove many unneeded !s from try!s in tests
Woo hoo! |
Describe the bug
I've been working on a Vapor REST API project. I'm running locally on my Mac at home, and hitting a MySQL DB hosted at DigitalOcean. I came back to work on it after leaving it the night before to find the Vapor app stopped in Xcode at this assertion:
I don't think there was an explicit query in progress, as it was just idling locally. The stack:
The queue has 16
nil
entries:To Reproduce
I didn't try to reproduce it.
Expected behavior
Ideally an error like this wouldn't crash the process. Maybe roll back the current transaction and throw an error?
Environment
Ventura 13.1 (22C65)
mysql-nio v1.4.0
mysql-kit v4.6.1
MySQL server v8.0.28, protocol version 10
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: