Problem: if building an index takes 10 hours, 2 hours of idleness is too easy to miss
Goal
When I build an index and it takes, say, 5 hours, it's not good that idle timeout is just 2 hours, it's too easy to miss.
We need some way to mitigate this problem
TODO / How to implement
I see two options, and we need to choose one of them:
- idle timeout depends on the last command duration (however, it increases chances to accumulate stale clones in DB Lab instance), or
- allow prolonging the session
- manually in Joe for N hours,
- or just using deletion protection. In the latter case, we may also need implementing the
stop
command
Acceptance criteria
As a user, when I build some huge index, I have a way to work with the results later, when it's convenient for me, not being obligated to appear during 2h window, the position of which in the timeline is not precisely defined in advance.