search

cryo28 / sidekiq_status

Extension to Sidekiq to pass job execution metadata such as status and result back to the client
MIT License
152 stars 53 forks source link

Doesn't integrate with sidekiq/testing #9

Closed stevenheidel closed 8 years ago

stevenheidel commented 11 years ago

When running with Sidekiq/testing always gives this error:

 SidekiqStatus::Container::StatusNotFound

With no backtrace.

cryo28 commented 11 years ago

@stevenheidel Pull requests are welcome :)

alex88 commented 10 years ago

Might be not raise exception in case env is test on line https://github.com/cryo28/sidekiq_status/blob/6d4f973a7ea4bd936fdb9c5663f80d65ce56f697/lib/sidekiq_status/container.rb#L149?

cryo28 commented 8 years ago

@stevenheidel Could you please try cryo28/sidekiq_status#3. This pull request should make SidekiqStatus less intrusive to Sidekiq's internal data structures and make sure it works well with Sidekiq::Testing.

cryo28 commented 8 years ago

Included in release 1.1

brandoncc commented 7 years ago

I would assume from the last two comments that this issue was fixed, but I am experiencing this problem with v1.2.0. Is there a way to make this gem work with the following?

require 'sidekiq/testing'
Sidekiq::Testing.inline!
jasdeepsingh commented 7 years ago

I'm having this same issue on 1.2.0. Instead of Sidekiq::Testing.inline! i'm using .drain to manually execute Sidekiq jobs on the worker queue.

jasdeepsingh commented 7 years ago

So, I tried both .drain and Sidekiq::Testing.inline! and I still get the SidekiqStatus::Container::StatusNotFound exception.