-
Notifications
You must be signed in to change notification settings - Fork 103
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
memqueue_test.go makes use of Redis #162
Comments
Perhaps it should not. But it is this way, because back in the days redisq backend did not exist and I needed some way to use taskq locally without S3/SQS. So I've replaced S3 with memqueue and left Redis as is because it is easy to run Redis locally. |
Happy to put together a PR to remove Redis from the memqueue_test.go file if you'd be willing to consider it. |
Looks related to #106? I guess we could use local storage with memqueue by default. |
Agreed, local storage would be the ideal fix. |
fix: Use localStorage for memqueue tests instead of Redis for #162
Any idea when a new release will be made? Looks like there's some fixes still in the Thanks! |
I think we can close #163 as this is merge now : |
Hey, I am trying to use the in-memory queue but it still appears to require redis (taskq 3.2.9):
I am running into:
So I guess that is not all that needs changing :-( Edit: It is a bug: #176 |
Perhaps I'm missing something obvious, but I don't see why
memqueue/memqueue_test.go
uses a Redis Ring. Given thatmemqueue/queue.go
is supposed to be an entirely in-memory queue, it seems odd that the unit tests are some weird hybrid of in-memory and Redis.The text was updated successfully, but these errors were encountered: