Problem

Before search in TM Maintenance we do assertion that TM has correct index.

To do so we trigger download endpoint to load TM into memory.

Looks like sometimes t5memory reacts incorrectly on status endpoint trigger after download and load do not produces expected result.

Solution

Redo assertion logic.

Lets first check if TM is empty and return empty list right away if true.

If not empty - lets still try to search for segments.

After that we check for for index - this way we guaranteed to have loaded TM.

And after that we can still trigger reorganise if index is brokken.

Test section

In current master try to make search in almost any TM in TM Maintenance.

Highly likely you'll get reorganise status right away - and this is a bug.

In fix branch - try the same and assert that reorganise doesn't popup for every TM.