You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2021. It is now read-only.
And rightly so, because if you were to print the created encoded key you will get something like:
b' eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzZWFyY2hfZmllbGRzIjp7ImRlc2NyaXB0aW9uIjp7fX0sImFwaV9rZXlfbmFtZSI6InNlYXJjaC1rZXkifQ.JezVQ4D6L76FadCvplQnCv8QpVJzxqy0dz-i_X4C4s0 '
indicating that this is a byte type value.
Work around
The workaround is to add .decode('utf8') to the signed_search_key variable in order to pass the key as a string type value and not a byte type one, like this:
And now you will be able to search to your heart's desire.
This doesn't happen on Python 3.3 (our current dependency). But Python 3.3 is already EOL, and ent-search users would rather not have to run EOL code in production in order to use this nifty client.
Cheers!
The text was updated successfully, but these errors were encountered:
Steps to reproduce
You will get this:
And rightly so, because if you were to print the created encoded key you will get something like:
indicating that this is a byte type value.
Work around
The workaround is to add
.decode('utf8')
to thesigned_search_key
variable in order to pass the key as a string type value and not a byte type one, like this:And now you will be able to search to your heart's desire.
This doesn't happen on Python 3.3 (our current dependency). But Python 3.3 is already EOL, and ent-search users would rather not have to run EOL code in production in order to use this nifty client.
Cheers!
The text was updated successfully, but these errors were encountered: