Gummikavalier
Gummikavalier
@pierre-lehnen-rc You can also scratch the multi instance and sticky sessions configuration from the test scenario completely. I just tested that to reproduce this highlighting issue, running one instance without...
7.7.2 docker image not yet available so I haven't been able to test it for that yet. But you can always use `DISABLE_DB_WATCHERS=false` variable in your deployment to work around...
For the record, I tested 7.7.3 and 7.8.0-rc.7 and this still happens on both. Very easily even in one instance, two client computers scenario. We'll probably have to wait longer...
Thanks, I'll test within two days. 👍
I cannot reproduce on RC 6.6.6. Probably has some particular condition to fulfill until it triggers.
Thanks! I still cannot replicate the issue. I tried and in these scenarios the global search as well as jumping to those messages work for us ok. "Room not found"...
Hi, yes, I tried. Global search works without issues for us. :disappointed_relieved:
Oh! Additional note; have you enabled `Global search` under `/admin/settings/Search -> Default provider`? We have that on.
We've had it enabled too during the beta times. It's getting weird... :disappointed:
I could not replicate on RC 6.13.0. But F5 / refresh was required to load the changes immediately after.