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

Locking gets triggered even if inline #4

Open
ntalbott opened this issue Feb 21, 2012 · 0 comments
Open

Locking gets triggered even if inline #4

ntalbott opened this issue Feb 21, 2012 · 0 comments

Comments

@ntalbott
Copy link

Even with Resque.inline = true, locking is still getting triggered, which means that in my tests Resque is trying to hit Redis, which I don't want it to do. I'd be happy to fix it, but I'm wondering: is this something that should be fixed here in resque-lock by checking Resque.inline?, or is it really a problem that Resque is triggering enqueue callbacks at all when inline is true?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ntalbott