ForestDB Index never reaches online if created with incoming workload already running

I don't have logs at the moment because of other testing but I wanted to capture what I observed. Let me know if this is something you can verify or need me to capture logs for.

-Create bucket
-Start write-heavy workload (very heavy)
-Create index on said bucket
-Observe that index never reaches "online", rather stays in "building"

I suspect this is because the indexer continues to receive mutations.

An improvement here would be to capture whatever the latest vbucket seq number is at the time of index creation/initial build and then transition to "online" once that is reached, obviously continuing to build (and likely being behind) with the new mutations coming in