Skip to content
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.

Sign up for GitHub

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

Jump to bottom

FIX charset=None was causing SubscriberProtocol.messageReceived to ne… #150

Merged
merged 2 commits into from Jul 6, 2023
Merged

FIX charset=None was causing SubscriberProtocol.messageReceived to ne… #150

merged 2 commits into from Jul 6, 2023

Commits on Jul 5, 2023

  1. FIX charset=None was causing SubscriberProtocol.messageReceived to ne… 

    …ver be called

If the charset = None in SubscriberProtocol then SubscriberProtocol .replyReceived will never call SubscriberProtocol.messageReceived due to u"message" when received will not match b"message" and u"pmessage" will not match b"pmessage" inside the if clauses therefore the code where messageReceived is called will never be reached. This is due to types of str and bytes will not match each other even if similar values are inside
    @EllieTheYeen
    EllieTheYeen committed Jul 5, 2023
    Configuration menu
    Copy the full SHA
    2910ab4 View commit details
    Browse the repository at this point in the history

  2. Update txredisapi.py

    @EllieTheYeen
    EllieTheYeen committed Jul 5, 2023
    Configuration menu
    Copy the full SHA
    0802931 View commit details
    Browse the repository at this point in the history