MagpieFourtyTwo

Over here (with latest nightly) it's working - at least most of the times: - after a fresh restart, *not a single login* succeeded within the usual two to three...

> the yet-again changed find count Perhaps you can even figure out why the login takes so extremely long (at least 25 to 30 and sometimes even up to 90...

In web browser pages load within fractions of a second, thus server is not an issue over here. Haven't timed the logins before, but would swear they were way faster...

+1 for P1 Although ... 1) I have never ever seen *that* many events before, with (nearly) the same coordinates, resulting in such a long select list, thus I guess...

> When I'm zoomed out across multiple cities it doesn't really work that well. Maybe - but, TBH, how common is this? Or do you prefer to do event hopping?...

Although routing was extremely "stubborn" that day, it hasn't happened since. I'll keep an eye on it, maybe I can get a more reproducible scenario.

New finding: Recalculation (resp. refresh in map) will not happen, *until current GPS location changes.* Of course it doesn't matter if the change has happened because of signal hopping or...

New finding: Recalculation (resp. refresh in map) will not happen, *until current GPS location changes.* Of course it doesn't matter if the change has happened because of signal hopping or...

Sorry for not responding to your PR, but due to #15726 we're still unable to run any tests at all with UM.

Seems as if this one is fixed meanwhile, at least had no obvious scenarios like the described anymore, thus let's close here.