Chris Gunther

I believe this is correct. The "expected arguments" is showing you the arguments from your assertion in array form. The "found arguments" is showing you the arguments of all the...

I've solved similar problems by asserting on how many jobs were queued, sometimes ensuring no jobs were queued. For example: ```ruby expect(MyJob.jobs.size).to eq(0) ```

I think I'm hitting something similar, using v7.1.12. (I've peeked at what's changed since up to v7.1.15 but nothing seems like it'd affect this) Here's my worker options: ```ruby sidekiq_options...

I dug further into this and believe I worked up a reproduction script: https://gist.github.com/cgunther/718379c4786e445e75a4e62ce612a9ee I think it's a latency issue. Using [toxiproxy](https://github.com/Shopify/toxiproxy) with just 20ms latency I can reliably reproduce...

Thanks! I ended up setting `SidekiqUniqueJobs.config.lock_timeout = 1` and after a day and a half in production, I've seen drastically fewer conflicts. My hunch is that's now higher than any...

I don't believe it solved it outright, but I do believe it's greatly improved. I've since bumped it up to `lock_timeout = 2` and seeing fewer conflicts. The conflicts are...

I think it's a sidekiq issue, not a toxiproxy issue. First, I think you need sidekiq to actually perform the job inline, not just enqueue (the default when including "sidekiq/testing",...

I deployed v7.1.26, so will keep an eye on things and report back. For now, I left `SidekiqUniqueJobs.config.lock_timeout = 2`, which probably negates the improvements you made in #728, as...

I think I'm hitting the same issue on Ubuntu 18.04 using v10.0.2 of the cookbook. What stands out in the Chef output on a fresh machine is the last line...

That error is likely coming from the end of the conditional here: https://github.com/sous-chefs/mysql/blob/f7c92af098bca2936a6189aec1344c63f8ad5c2d/libraries/mysql_service_base.rb#L126 I hit a similar issue as it seemed like `node['apparmor']` was `nil` for me, so it fails...