sidekiq-unique-jobs | Prevents duplicate Sidekiq jobs | Application Framework library

by mhenrixon Ruby Version: v8.0.2 License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | sidekiq-unique-jobs Summary

sidekiq-unique-jobs is a Ruby library typically used in Server, Application Framework, Ruby On Rails applications. sidekiq-unique-jobs has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

This gem adds unique constraints to sidekiq jobs. The uniqueness is achieved by creating a set of keys in redis based off of queue, class, args (in the sidekiq job hash). By default, only one lock for a given hash can be acquired. What happens when a lock can't be acquired is governed by a chosen Conflict Strategy strategy. Unless a conflict strategy is chosen. This is the documentation for the main branch. You can find the documentation for each release by navigating to its tag. Here are links to some of the old versions.

Support

Quality

Security

License

Reuse

Support

sidekiq-unique-jobs has a medium active ecosystem.

It has 1311 star(s) with 260 fork(s). There are 16 watchers for this library.

It had no major release in the last 12 months.

There are 46 open issues and 350 have been closed. On average issues are closed in 87 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of sidekiq-unique-jobs is v8.0.2

Quality

sidekiq-unique-jobs has 0 bugs and 0 code smells.

Security

sidekiq-unique-jobs has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

sidekiq-unique-jobs code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

sidekiq-unique-jobs is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

sidekiq-unique-jobs releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 61054 lines of code, 753 functions and 439 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed sidekiq-unique-jobs and discovered the below as its top functions. This is intended to give you an instant insight into sidekiq-unique-jobs implemented functionality, and help decide if they suit your requirements.

Executes the given block with the given name and execution time .
Delete the queue
This method is called when a worker is not .
Determines a notification .
Execute a job with the given id .
Enqueue a job
Searches a redis pattern .
Builds an exception hash for an exception and the message .
Resets the completion for the given task .
Delete all hashes from the batch .

Get all kandi verified functions for this library.

sidekiq-unique-jobs Key Features

No Key Features are available at this moment for sidekiq-unique-jobs.

sidekiq-unique-jobs Examples and Code Snippets

No Code Snippets are available at this moment for sidekiq-unique-jobs.

Community Discussions

Trending Discussions on sidekiq-unique-jobs

ElasticSearch deployment issue: NameError: uninitialized constant Elasticsearch

In production Sidekiq add job to history, but doesn't execute it (Sidekiq + Redis + EC2 + Cloud66)

QUESTION

ElasticSearch deployment issue: NameError: uninitialized constant Elasticsearch

Asked 2022-Feb-23 at 14:15

I am deploying my rails app via AWS. During the deployment I get the following error.

Automatic configuration of the sidekiq middleware is no longer done. Please see: https://github.com/mhenrixon/sidekiq-unique-jobs/blob/master/README.md#add-the-middleware

This version deprecated the following sidekiq_options

sidekiq_options lock_args: :method_name

It is now configured with:

sidekiq_options lock_args_method: :method_name

This is also true for Sidekiq.default_worker_options

We also deprecated the global configuration options:

default_lock_ttl

default_lock_ttl=

default_lock_timeout

default_lock_timeout=

The new methods to use are:

lock_ttl

lock_ttl=

lock_timeout

lock_timeout= Removing intermediate container 058b1862fa23 ---> d58eac1f9787 Step 22/28 : COPY --chown=app:app . . ---> f91e7b24a602 Step 23/28 : RUN bundle exec rake assets:precompile ---> Running in 49531771f9ca rake aborted! NameError: uninitialized constant Elasticsearch /home/app/webapp/config/initializers/elasticsearch.rb:11:in ' /usr/local/rvm/gems/ruby-2.6.8/gems/bootsnap-1.10.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:48:in load' /usr/local/rvm/gems/ruby-2.6.8/gems/bootsnap-1.10.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:48:in load' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/engine.rb:666:in block in load_config_initializer' /usr/local/rvm/gems/ruby-2.6.8/gems/activesupport-6.0.4.6/lib/active_support/notifications.rb:182:in instrument' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/engine.rb:665:in load_config_initializer' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/engine.rb:625:in block (2 levels) in ' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/engine.rb:624:in each' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/engine.rb:624:in block in ' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/initializable.rb:32:in instance_exec' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/initializable.rb:32:in run' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/initializable.rb:61:in block in run_initializers' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/initializable.rb:50:in each' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/initializable.rb:50:in tsort_each_child' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/initializable.rb:60:in run_initializers' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/application.rb:363:in initialize!' /home/app/webapp/config/environment.rb:5:in ' /usr/local/rvm/gems/ruby-2.6.8/gems/bootsnap-1.10.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require' /usr/local/rvm/gems/ruby-2.6.8/gems/bootsnap-1.10.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in require' /usr/local/rvm/gems/ruby-2.6.8/gems/zeitwerk-2.5.4/lib/zeitwerk/kernel.rb:35:in require' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/application.rb:339:in require_environment!' /usr/local/rvm/gems/ruby-2.6.8/gems/railties-6.0.4.6/lib/rails/application.rb:523:in block in run_tasks_blocks' /usr/local/rvm/gems/ruby-2.6.8/gems/sprockets-rails-3.4.2/lib/sprockets/rails/task.rb:61:in `block (2 levels) in define' Tasks: TOP => environment (See full trace by running task with --trace) The command '/bin/sh -c bundle exec rake assets:precompile' returned a non-zero code: 1

[Container] 2022/02/23 11:37:32 Command did not exit successfully docker build --build-arg RAILS_ENV --build-arg DATABASE_URL --build-arg REDIS_URL --build-arg SECRET_KEY_BASE -t $REPOSITORY_URI:latest . exit status 1 [Container] 2022/02/23 11:37:32 Phase complete: BUILD State: FAILED [Container] 2022/02/23 11:37:32 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: docker build --build-arg RAILS_ENV --build-arg DATABASE_URL --build-arg REDIS_URL --build-arg SECRET_KEY_BASE -t $REPOSITORY_URI:latest .. Reason: exit status 1 [Container] 2022/02/23 11:37:32 Entering phase POST_BUILD [Container] 2022/02/23 11:37:32 Running command echo Build completed on date Build completed on Wed Feb 23 11:37:32 UTC 2022

[Container] 2022/02/23 11:37:32 Running command echo Pushing the Docker images... Pushing the Docker images...

[Container] 2022/02/23 11:37:32 Running command docker push $REPOSITORY_URI:latest The push refers to repository [413249046650.dkr.ecr.eu-west-1.amazonaws.com/legitimate-development] An image does not exist locally with the tag: 413249046650.dkr.ecr.eu-west-1.amazonaws.com/legitimate-development

[Container] 2022/02/23 11:37:32 Command did not exit successfully docker push $REPOSITORY_URI:latest exit status 1 [Container] 2022/02/23 11:37:32 Phase complete: POST_BUILD State: FAILED [Container] 2022/02/23 11:37:32 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: docker push $REPOSITORY_URI:latest. Reason: exit status 1 [Container] 2022/02/23 11:37:32 Expanding base directory path: . [Container] 2022/02/23 11:37:32 Assembling file list [Container] 2022/02/23 11:37:32 Expanding . [Container] 2022/02/23 11:37:32 Expanding file paths for base directory . [Container] 2022/02/23 11:37:32 Assembling file list [Container] 2022/02/23 11:37:32 Expanding imagedefinitions.json [Container] 2022/02/23 11:37:32 Skipping invalid file path imagedefinitions.json [Container] 2022/02/23 11:37:32 Expanding imagedefinitions2.json [Container] 2022/02/23 11:37:32 Skipping invalid file path imagedefinitions2.json [Container] 2022/02/23 11:37:32 Phase complete: UPLOAD_ARTIFACTS State: FAILED [Container] 2022/02/23 11:37:32 Phase context status code: CLIENT_ERROR Message: no matching artifact paths found

The file referenced in the line below the error is:

...

ANSWER

Answered 2022-Feb-23 at 14:15

That file uses the Elasticsearch constant in Elasticsearch::Client, but Ruby does not know it.

Do you have the elasticsearch gem in the Gemfile in a group that is included in production? If yes, does it have require: false?

Source https://stackoverflow.com/questions/71236500

QUESTION

In production Sidekiq add job to history, but doesn't execute it (Sidekiq + Redis + EC2 + Cloud66)

Asked 2020-Dec-11 at 09:27

My app have an import function that'll execute a Sidekiq Worker and import a bunch of CSV rows, saving them to my database. This works fine when I execute Sidekiq in my local machine, but when I deploy the code to production Sidekiq will execute the job correctly only once. When I use the import function a second time the job goes directly to the history pile in Sidekiq, and the logic inside the worker is never executed. It's really strange because it throws no error and it's like the job was executed correctly. For staging I'm using Redis in AWS Elastic Cache.

...

ANSWER

Answered 2020-Dec-09 at 17:10

sidekiq_options queue: "import_worker", lock: :until_executed, retry: false

Source https://stackoverflow.com/questions/65215302

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install sidekiq-unique-jobs

Add this line to your application's Gemfile:.

Support

Want to show me some ❤️ for the hard work I do on this gem? You can use the following PayPal link: https://paypal.me/mhenrixon1. Any amount is welcome and let me tell you it feels good to be appreciated. Even a dollar makes me super excited about all of this.

Find more information at: