Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:33:46Zhttps://gitlab.torproject.org/legacy/trac/-/issues/28319accept a reasonably live consensus for path selection2020-06-13T15:33:46Zteoraccept a reasonably live consensus for path selectionWhen I fixed guard selection in #24661, tor said:
```
Nov 05 15:29:55.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
```
Maybe this is a logging issue, mayb...When I fixed guard selection in #24661, tor said:
```
Nov 05 15:29:55.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
```
Maybe this is a logging issue, maybe it's another constraint we need to fix.
See the full log in:
https://trac.torproject.org/projects/tor/ticket/24661#comment:13Tor: 0.4.0.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/28255verify guard selection consensus expiry constraints2020-06-13T15:33:32ZTaylor Yuverify guard selection consensus expiry constraintsThe hypothesis in #23605 is that bootstrapping can get stuck at #23605 if there is enough clock skew for the consensus to be expired but still "reasonably live". Let's verify this and try to record more details.The hypothesis in #23605 is that bootstrapping can get stuck at #23605 if there is enough clock skew for the consensus to be expired but still "reasonably live". Let's verify this and try to record more details.Tor: 0.4.0.x-finalteorteor