Open mkroman opened 4 years ago
closed by #2768
@lyoshenka that PR does not solve this particular issue - the PR just makes the lbrynet
daemon able to run, but there's still a silent problem with connection resets from the API when using Python 3.8 as described in this issue which I haven't tracked down.
@mkroman Thanks for letting me know. I've reopened the issue. If you do track down a solution, we would be grateful :-)
This error seems to be documented in the aiohttp project.
See https://github.com/aio-libs/aiohttp/issues/5818, https://github.com/aio-libs/aiohttp/issues/4724, https://github.com/aio-libs/aiohttp/issues/3507. In those cases they use Python 3.6 and 3.7, while the error in LBRY is only visible with Python 3.8+.
This issue should be solved with #3362.
The solution is just using a newer aiohttp
. I tried aiohttp==3.6.2
because that is the version in the repositories in Ubuntu 20.04. To test I use Python 3.8 in Ubuntu, and Python 3.9 in Arch, and they both seem to work fine.
After some testing and some discussion with @er013 it's apparent that there's some kind of silent incompatibility with Python
3.8.x
that's not present in Python3.7.6
.When
lbrynet
(0.58.1
) is started using Python3.8.1
, requests to the API will be met with a connection reset:However, if the same
lbrynet
version (0.58.1
) is installed with Python3.7.6
the API will respond successfully: