Matti Vapa

We are facing this issue in the `vagrant up` stage when trying to pull the production DB. Even though the host has valid ssh keys, a password is needed to...

I just tested locally to remove the `version` element from all the `docker compose` `.yml` files. Everything seems to work as before, and the warnings are gone.

Just got hit by this too on 2.3.5-p1 when a campaign caused a surge in traffic. Hotfixed by doing what @mflott suggested and forcing the controller code take the `getNotCacheableResult`...

Initial testing suggests that adding this index on the `search_query` table may resolve the issue. I did not observe much increase in write loads, but this is yet to be...