-
Notifications
You must be signed in to change notification settings - Fork 679
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
Possible bad alignment of data when decoding the query event #380
Comments
with encoding utf8mb4. TODO - file a bug report
@the4thdoctor |
Thanks :) |
Hi, any update on this? |
@dongwook-chan any news? ta! |
we run into the same issue, want to check if there is any update for this issue. |
@ruiyang2015 cc. @the4thdoctor |
No worries, I had a similar issue last year. I hope all is fine now :) |
I confirm the issue is now solved 🥳 |
@the4thdoctor |
I have issues when processing the query event.
The problem is not present in version 0.26.
It seems it was introduced in version 0.28 and it's still present in 0.30.
When capturing the query event sometimes the first character of the query is truncated and then when the decode moves forward unexpected data appears crashing the binlogstream process because of utf-8 issues.
It seems to me an issue with the wrong read starting point and length for the query event packet
Server version Mariadb 10.6.5-MariaDB-log Source distribution
Python version Python 3.9.12
How to reproduce the issue
Start the database server and run the following script (adjust your connection parameters accordingly):
Create a new table on the server:
The script will output something like this.
Thanks!
The text was updated successfully, but these errors were encountered: