mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-26 07:25:56 +03:00
[GH-ISSUE #790] [BUG] rate.NewSemaphore: type conversion failure (MakeRedisClient error?) #385
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#385
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gwkline on GitHub (Nov 29, 2023).
Original GitHub issue: https://github.com/hibiken/asynq/issues/790
Originally assigned to: @hibiken on GitHub.
Describe the bug
When trying to create a new semaphore using the rate package, I am getting the following error:
I believe this is happening because calling
asynq.MakeRedisClient()on aasynq.RedisClientOptis returning a*redis.Clientwhich doesn't implement all methods required byredis.UniversalClient. Maybe this is because of a mismatch between the go-redis version? I'm not quite sure.To Reproduce
Expected behavior
When passing a valid
asynq.RedisClientOpttorate.NewSemaphore, there should not be a type coercion error.Environment (please complete the following information):
@kamikazechaser commented on GitHub (Dec 6, 2023):
Looking at your environment, The x package is not compatible with v0.24.x at the moment. I can see we reverted it back to go-redis/v8. Could you try running your snippet when compiled with an older version of
github.com/hibiken/asynq?@kamikazechaser commented on GitHub (Dec 7, 2023):
Could you test https://github.com/hibiken/asynq/pull/796 and let me know if it fixes this issue.
cc/ @amaury1729
@gwkline commented on GitHub (Dec 7, 2023):
@kamikazechaser #796 does appear to solve this issue!