Ivan Larionov

I don't think it's an M1 issue. I saw this happening on Intel Mac as well. Restart of EUL usually fixed it for a while.

Another variant is to split API and downloader parts to different projects.

I see the same issue. We use AWS AMIs with pre-baked omnibus chef and `test-kitchen` > 1.4.2 doesn't work. Error: ``` sudo: /bin/chef-solo: command not found D Cleaning up local...

Workaround is to set this under `provisioner`: ``` ruby chef_omnibus_root: /opt/chef ```

Just tested the latest Chrome, macOS Catalina and Razer DeathAdder mouse and it works just fine. Will retest with the latest Chrome on Big Sur / X17 mouse and report...

Tried the latest Chrome, macOS Big Sur and EVGA X17 and still see this issue. Could be mouse specific or Big Sur specific I guess.

Fun fact – setting scrolling speed to max "Fast" actually reduces the amount of zoom in/out in Google Maps (still not smooth nor usable tho).

Seeing some issues with redis 5.x.x gem and `BACKGROUND=yes` too, scheduler exits silently with 0 code, but background process is not running, from what I gathered in `strace -f` child...

I tried the latest version and it still silently fails in background mode (I wish logging wasn't so broken for `resque-scheduler`). `strace` shows some errors like: ``` rake aborted! Redis::CannotConnectError:...

> This one is a new one to me. I wish I knew what that system error was. Reverting to redis 4.8 fixes it? Yes.