Add error logging for crc32 validation failures.

[why-arong]

Description

This PR add logging for situations where CRC32 validation does not pass.

By monitoring these failures, we can ensure data integrity throughout the application.

[sean-k1]

Suggested change

	if byte_data == footer:
	self._is_event_valid = True
	else:
	self._is_event_valid = False
	logging.error(
	f"An CRC32 has failed for the event type {self.event_type}, "
	"indicating a potential integrity issue with the data."
	)
	self._is_event_valid = True if byte_data == footer else False
	if not self._is_event_valid:
	logging.error(
	f"An CRC32 has failed for the event type {self.event_type}, "
	"indicating a potential integrity issue with the data."
	)

@why-arong
I think this looks more readable, what do you think?
I think the code you wrote is good, too.

[why-arong]

I think that code reads better!

How about error message? Is there any additional information we can provide besides 'self.event_type'??

[sean-k1]

I think that's enough

[why-arong]

@sean-k1

python-mysql-replication/pymysqlreplication/binlogstream.py

Lines 553 to 558 in 1d2c8ab

	logging.log(
	logging.WARN,
	"""
	Before using MARIADB 10.5.0 and MYSQL 8.0.14 versions,
	use python-mysql-replication version Before 1.0 version """,
	)

How do you feel about not writing the code like logging.log(logging.ERROR, ~~~)? Unless I need to set the log level dynamically, I think logging.error(~~~) is more intuitive, so that's how I wrote it!

[sean-k1]

@sean-k1

python-mysql-replication/pymysqlreplication/binlogstream.py

Lines 553 to 558 in 1d2c8ab

	logging.log(
	logging.WARN,
	"""
	Before using MARIADB 10.5.0 and MYSQL 8.0.14 versions,
	use python-mysql-replication version Before 1.0 version """,
	)

How do you feel about not writing the code like logging.log(logging.ERROR, ~~~)? Unless I need to set the log level dynamically, I think logging.error(~~~) is more intuitive, so that's how I wrote it!

logging.error is more better👍

[sean-k1]

LGTM Thanks your hard work!