add ErrorHandling class, refactor spec
correct the raven config class
correct the raven test
add a fake method for getting an exception
require error_handling
add new TestError class to test exceptions
add correct error class to test
add rescue block to raven send
make method a class method and add a test Travis.config.dns
add error the repos to test error
remove carla method in repos
add a fake error in repos
delete carla method
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
When log is aggregated and archived we don't have a way to return it in
JSON format, only text format. Till recently we were returning a text
response or a redirect to S3 even if Accept header was set only to JSON.
This commit fixes it.
after query param allows to get only parts that come after a specified
number, for example "after: 10" will download only parts that come after
10th part.
If a value is provided with a request to update the record, we should
not nullify it. We don't send decrypted private values to the client, so
if client provides it, it's probably pasted by the user.
When env var is changed from private to public, we didn't nullify it, so
someone doing that could miss exposing it. To minimise the risk of
exposing any secure info we'll now nullify the value.
