-
Notifications
You must be signed in to change notification settings - Fork 65
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
[Bug] Vec<u8> is recognised as Array rather than Bytes #296
Comments
I can take this up we need a different |
Hi @dracarys18, Unfortunately I'm not sure how to do this on stable rust at the moment without specialization, but feel free to submit a PR if you can make it work. After looking at this a bit more - If I'm reading this correctly it looks like I think there's a few ways to work around this, but they have some downsides:
For the next major version I'll probably remove the |
@aembke I like the idea of last point can we make a feature flag for this so it wont break for others and slowly release it in the next release |
Sounds good. In 9.4.0 there a new FF |
Oh that's awesome! Thanks @aembke |
Added in 9.4.0 |
Fred version - 9.2.1
Redis version - 7.0.1
Platform - mac
Deployment type - cluster|sentinel|centralized
Describe the bug
For the following example below, Fred throws and error
value: Redis Error - kind: InvalidArgument, details: Invalid argument type: Array
while it's a valid type.To Reproduce
Steps to reproduce the behavior:
hsetnx
function withVec<u8>
as value type.Logs
(If possible set
RUST_LOG=fred=trace
and run with--features debug-ids
)Redis Error - kind: InvalidArgument, details: Invalid argument type: Array
The text was updated successfully, but these errors were encountered: