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.

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

NameError (uninitialized constant Resque::Plugins::UniqueJob) #54

Open
leoplct opened this issue Jun 2, 2020 · 4 comments
Open

NameError (uninitialized constant Resque::Plugins::UniqueJob) #54

leoplct opened this issue Jun 2, 2020 · 4 comments

Comments

@leoplct
Copy link

leoplct commented Jun 2, 2020

I have installed the gem, required from initializers and restarted server. But I get this error.

Gemfile
gem "resque-loner"

config/initializers/resque.rb
require 'resque-loner'

RefreshItemsJob

class RefreshItemsJob < ApplicationJob
  include Resque::Plugins::UniqueJob
@kjleitz
Copy link

kjleitz commented Dec 30, 2020

Sigh, yeah I get this as well, after upgrading to Resque v2.0.0—I think bundler downgraded resque-loner on my machine from v1.3.0 to v0.1.1 because v1.3.0 has a dependency on resque (~> 1.0) which isn't satisfied by 2.0.0, so it went with the latest version of resque-loner that didn't restrict the resque version.

This gem hasn't seen activity in a very very long time. Last commit was in 2014. No PRs or issues have been addressed in about as long. Might be time for a fork.

@pboling
Copy link
Member

pboling commented Jan 10, 2022

@leoplct @kjleitz resque-solo was a more recent rewrite/fork of this gem, and my own resque-unique_in_queue was a rewrite/fork of that. I'd recommend starting there, though it hasn't been been updated for Resque v2.0.0, it is far more updated than anything else. Happy to hand off maintenance to an interested party.

  • resque-unique_at_runtime
    • Ensure that jobs are unique at runtime. A rewrite, and update, of resque-lonely_job. Upgrades should be mostly find/replace seamless. Compatible with resque-unique_by_arity, and resque-unique_in_queue.
  • resque-unique_by_arity
    • Configure exacting specification of what "unique" means for a job. Compatible with resque-unique_at_runtime, and resque-unique_in_queue.
  • resque-unique_in_queue
    • Ensure that jobs are unique at queue-time (and in-queue). A rewrite, and update, of resque-solo, which was a rewrite of resque_loner. Upgrades should be mostly find/replace seamless. Compatible with resque-unique_by_arity, and resque-unique_in_queue.

@iloveitaly
Copy link

@pboling could you transfer the repo to the resque org? If folks are interested in maintaining they can pick up the torch! It would be great if you could submit a PR to add this comment to this repo to explain to folks their options.

@pboling
Copy link
Member

pboling commented Jan 11, 2022

Yeah, I will work on that. Great idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants