-
Notifications
You must be signed in to change notification settings - Fork 451
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
UnicodeDecodeError: unexpected end of data in on_tracker_error_alert
#7406
Comments
Sentry issue: TRIBLER-16C |
Closed
kozlovsky
added a commit
to kozlovsky/tribler
that referenced
this issue
Jun 8, 2023
kozlovsky
added a commit
to kozlovsky/tribler
that referenced
this issue
Jun 8, 2023
kozlovsky
added a commit
to kozlovsky/tribler
that referenced
this issue
Jun 8, 2023
kozlovsky
added a commit
to kozlovsky/tribler
that referenced
this issue
Jun 9, 2023
kozlovsky
added a commit
that referenced
this issue
Jun 9, 2023
Fixes #7406 UnicodeDecodeError in on_tracker_error_alert
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here:
It is a regression of #5740: f-string formatting of the
logging.error
output should also be placed inside the following try/except block to have protection from UnicodeDecodeError.As an additional protection, we can add a helper function like
alert_to_str
and use it in all places where we have{alert}
formatting to be sure that all alerts can be safely converted to strThe text was updated successfully, but these errors were encountered: