Closed KyleMaas closed 3 years ago
I can see now where this could happen if you were not connected and you tried to view a thread that wasn't in the database. But if the root of the thread is in the database, it looks like it should operate correctly and seems to in practice.
It appears (and I haven't debugged this, so I don't know why this would be) that if you're not connected to another peer with data and you try to view a thread, the Thread page will wait (with no indication it's doing anything) until you're connected. Then it loads. Only thing I can think of is that maybe it's hanging at the stage where it tries to get a tangle and rather than give up after a bit and query the database directly it just stops. But that's just a hypothesis - really needs proper debugging.