Bruno Degomme
Bruno Degomme
I had a similar issue, and for me the issue was that the Cop name was incorrect. Apparently rubocop automatically removes comments disabling non-existant cops.
I had the same issue, the solution was to add '--autoplay-policy=no-user-gesture-required' to the puppeteer args (and actually joining the audio of the meeting)
if anyone reading this is wondering : as far as I can understand from the source code, when a first call to throttle! fails the throttler will block for `block_for`...
See https://github.com/ixti/sidekiq-throttled/issues/52#issuecomment-412911238 : when a job is throttled it's put back at the end of the queue. The issue with other jobs not running is due to the cooldown ```ruby...
yes that's right. Maybe for you it makes sense to increase `cooldown_threshold` even more, but make sure to do it gradually so you know your Redis server can handle it
Yes you should put this in the sidekiq initializer. What did you set SIDEKIQ_COOLDOWN_PERIOD and SIDEKIQ_COOLDOWN_THRESHOLD to? Have you tried 1 and 5000 respectively? Then it should take around ~30s...
thank you @lorikku! Shouldn't `channelCount: { exact: 1 }` have led to a mono file instead of stereo? Any clue how to end up with a mono file?
I had the same issue and this worked for me! thanks a lot @SoumyaRanjanPatnaik