hs-v3: Client fails to reach service before 90% bootstrap
It appears that between bootstrap 85% and 90%, it is when the consensus is fetch and we wait on it before trying to establish a first circuit which would bring us to 90%.
Before that, we have no live consensus so setting the hsdir index to a node_t fails because it requires a live consensus to do so. Because of that, a client just can't reach any service because it can not build an hashring.
I think we should require any client actions to have a live consensus which would mean to either stall the SOCKS request until we have it (seems to be around 90% bootstrap) or we close it right away and ask to come back later.
I would go for stalling and try once the live consensus is here.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information