Skip to content

Locking gets triggered even if inline #4

@ntalbott

Description

@ntalbott

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions