Unicorn, which we use to serve the API, uses forked workers that need
only one connection per instance. Sidekiq on the other hand runs several
instances in memory, so it needs a higher concurrency setting. This
commit introduces a way to set sidekiq db pool using
SIDEKIQ_DB_POOL_SIZE
For some reason pool is set to 1 and I can't find the source of this
setting, so for now, just to fix the immediate problem I'm setting it
manually in sidekiq.rb
See below for all the commit messages squashed into this one...
add a test
delete empty space
add job_cancellation worker
change id
change job_id param
add job restart worker
add require to sidekiq.rb
change params
add test for job restart and cancellation
add test for job restart
update build.rb improve build spec
update job restart with correct response, add test to chack for correct response when restarting job
:
add require sidekiq to the sidekiq.rb
update Gemfile.lock
bump travis-sidekiqs
correct require statement
fix another request
connect to the database
add current user
add current user correctly
add current user correctly
add puts to see were in the condition we are
missing invertted comma
add comments to the worker
I HAVE NO IDEA
Revert "I HAVE NO IDEA"
This reverts commit 8bd1259bf4ea1b479f9391847a4700b7b15efe57.
change the id and source to symbols in the params because siedekiq expects that
add more printout
setup database connection, metrics and notification
correct the test
