Jonathan Moody

>I started scribe from scratch (and with the original code instead of my modifications), and it seems it's up to date now, so that snapshot was broken somehow Good to...

Just saw a new `EADDRINUSE` problem when running lbry-sdk tests against this hub branch. https://github.com/moodyjon/lbry-sdk/actions/runs/3911989925/jobs/6686050669 Converting this to draft status while investigating.

I did some work on `StatusServer.start()` to make it retry to overcome transient `EADDRINUSE`. It got a bit more complicated in order to handle cases like `HOST=::,0.0.0.0`, `HOST=0.0.0.0,::`, `HOST=myserver1,myserver2`, etc....

Have not seen `EADDRINUSE` since that one occurrence. Not sure what the root cause of that was. Possible infrastructure?

This blocks linking to a new version of hub in lbry-sdk/setup.py. I think the change should be reverted, or we go to a higher version of protobuf that does not...

Herald.go implemented an optional `--chain` argument this way: https://github.com/moodyjon/herald.go/blob/e070e8a51ead553f31680e99d6cacd56bfcf3a2c/server/server.go#L275

The point of commit https://github.com/lbryio/hub/pull/113/commits/5b1d4bff5c7c57b8613a147fc4d2a89bb9e0d4cb Is to cut off indexing of all the nested things inside extensions. The fields which are “runtime” can be queried, but not as time-efficiently as...

https://www.elastic.co/guide/en/elasticsearch/reference/8.3/analysis.html

Modified `scripts/test_claim_search.py` and tested a few text queries against spvNN.lbry.com. The hubs that are responsive to connection are usually replying within the 10s timeout. But I did get one close...

Perhaps the thing to be done here is spread the load around more. It looks like the SDK selects the one with the lowest latency SPVPong response. This could be...