Andriy Biletsky

Does not work with encrypted SSH keys on macos 12.2

1

## Describe the bug Pyinfra is unable to connect when authenticating with an SSH key. Supplying or ommitting ssh_key_password in the inventory or as a cli argument does not change...

Decouple chainquery data access from the database and chainquery daemon

5

I propose implementing a rate-unlimited HTTP GraphQL API for accessing the data. For example, to retrieve a claim by claim_id, request: ``` query { Claim(claim_id: "6769855a9aa43b67086f9ff3c1a5bacb5698a27a") { fee sd_hash }...

[WIP] Fix wallet

1

Replace wallet error string matching with error names.

Do not log all JSON-RPC parameters

1

Call parameters are logged now like this: ```..."params":{"any_tags":[],"channel_ids":["deed21cf85c453e074b95949098fcd0c3dc65d69","9ab8d447066d328d8ebd115f725e701bd6fce93a","82f1d8c257d3e76b711a5cecd1e49bd3fa6a9de9","0871b29c7db6f1ec013694c8146f772539fcffa3","537305bc1bd71e2a5d76efacd607fd0f4d95da0c","c07ce3862335cfe9ba72054347c4ea7808ce4eaa","0e1aff187fbd3d2b2b16e5e8c213d3e782dafa98","a1303dc6a592605b08d60cac19ecbc1c877d7de7","2a294ea41312c6da8de5ebd0f18dbfb2963bb1a4","d6350f9158825662b99e4b5e0442bcc94d39bc11","3e7bb536a1b755b6eb64043ae3fa933d5935eaad","0518c93a80efeaf06fb4ac4d3fa72cc6390ac100","b8a2d928a3d3f44457a10abd0539b84e4a29c286","564789ffe2420980dcf9e00c4746feb5bc0daad0","7364ba2ac9090e468855ce9074bb50c306196f4c","e33372c0d8b2cdd3e12252962ee1671d66143075","3e63119a8503a6f666b0a736c8fdeb9e79d11eb4","1ce5ac7bab7f2e82af02305ced3c095e320b52e5","588ff6ffc72884e61e8d19a9412d6db9ec67167e", ...``` This is excessive and clogs up the logs. Would be good to limit the number of parameters logged to some reasonable...

Use lbrytv API instead of local lbrynet client

1

We can remove the need to have a running lbrynet instance nearby by using grpc interface for [LBRY hub](https://github.com/lbryio/hub/) instead. After this is done, we can drop lbrynetClient setup code...

Right now it works by calling `metrics.StreamsRunning` at the start of binary stream request, which is not suitable for HLS as each HLS stream is guaranteed to incur a multitude...

Things to watch: * General HTTP response statuses * TTFB * Blob retrieval errors/successes/timings A good place to start is to look at existing metrics, which are declared in `internal/metrics`.

It would be useful to collect metrics which would allow us to assess our clients network capacity, such as: - client location - assigned player - average bandwidth to the...

If a new claim version is uploaded before query cache invalidation timeout, it's possible for the old claim version to be retrieved and subsequently cached in downstream CDN.