Jonathan Moody

Putting this in draft status, pending fix for some (probably) unrelated test failures: 1) (pending fixes) https://github.com/lbryio/lbry-sdk/pull/3624 2) (hub? fixes needed) https://github.com/lbryio/hub/issues/55

I have synced up to head-of-line, and am running tests to asses where the next pain point is in the tests. Most of this is going on in moodyjon/lbry-sdk actions...

Out of 20 runs, I got 5 failures. `test_connection_drop_still_receives_events_after_reconnected` was seen 2 times, the others 1 time. [py39_2 ci failures.txt](https://github.com/lbryio/lbry-sdk/files/9315430/py39_2.ci.failures.txt) `test_file_save_stop_before_finished_streaming_only_wait_for_start` is one I had been modifying heavily, ***though I...

> pick 2 random bytes > query hub for all streams starting with those 2 random bytes (should be 270-350 claims) Are you talking about searching by stream name or...

https://github.com/lbryio/lbry-sdk/blob/ba60aeeebc1cf8e91d4127345e95091907c96d7b/scripts/generate_json_api.py#L466 Looks like the "Usage:" section of the docstring determines whether "is_required" will be true. But the argument also needs to be in the "Options:" section to be detected and...

I believe the exception contents line up with this assert: https://github.com/lbryio/lbry-sdk/blob/b8867cd18cf32e61af52abe09664a8dd9e7d6af1/lbry/dht/protocol/protocol.py#L450 However, the *sender* has this assert: https://github.com/moodyjon/lbry-sdk/blob/ebfca6bc6f21cc651b14c95683e10f8c1a42d208/lbry/dht/protocol/protocol.py#L651 Neither assert is particularly new. So could it be that the message...

You might be able to find a cause by investigating lbrynet.log: https://lbry.com/faq/how-to-find-lbry-log-file

Also version 0.53.2 of lbry-desktop had problems. https://github.com/lbryio/lbry-desktop/blob/master/CHANGELOG.md Check your version.

Another one: https://github.com/moodyjon/lbry-sdk/runs/8285365273?check_suite_focus=true

(deleted, moved to right issue)