Connection reset from API when using Python 3.8 #2769
Labels
Comments
Merged
|
closed by #2768 |
|
@lyoshenka that PR does not solve this particular issue - the PR just makes the |
|
@mkroman Thanks for letting me know. I've reopened the issue. If you do track down a solution, we would be grateful :-) |
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 7, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. If Python 3.8 is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ``` Python 3.9 does not work either, as it fails in the compilation of `plyvel`.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 8, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. If Python 3.8 is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ``` Python 3.9 does not work either, as it fails in the compilation of `plyvel`.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 9, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. If Python 3.8 is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ``` Python 3.9 does not work either, as it fails in the compilation of `plyvel`.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 10, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8 is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ``` Python 3.9 does not work either, as it fails in the compilation of `plyvel`.
This was referenced Jul 10, 2021
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 10, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8 is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ``` Python 3.9 does not work either, as it fails in the compilation of `plyvel`.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 11, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8+ is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ```
|
This error seems to be documented in the aiohttp project. See aio-libs/aiohttp#5818, aio-libs/aiohttp#4724, aio-libs/aiohttp#3507. In those cases they use Python 3.6 and 3.7, while the error in LBRY is only visible with Python 3.8+. |
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 11, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8+ is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ```
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 11, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8+ is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ```
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 11, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 11, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 11, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8+ is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ```
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 12, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8+ is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ```
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 12, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. In this case it will raise the exception `aiohttp.ClientConnectionError` We want to print this exception for the future to know what went wrong.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 12, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 12, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8+ is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ```
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 12, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8+ is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ```
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 12, 2021
Because of issue lbryio#2769 at the moment the `lbrynet` daemon will only work correctly with Python 3.7. The `deadsnakes` personal package archive (PPA) provides Python 3.7 for Ubuntu distributions that no longer have it in their official repositories like 18.04 and 20.04. If Python 3.8+ is used, the daemon will start but the RPC server may not accept messages, returning the following: ``` Could not connect to daemon. Are you sure it's running? ```
This was referenced Jul 12, 2021
|
This issue should be solved with #3362. The solution is just using a newer |
eukreign
pushed a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 19, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 20, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. In this case it will raise the exception `aiohttp.ClientConnectionError` We want to print this exception for the future to know what went wrong.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Jul 20, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Aug 21, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Sep 12, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Sep 12, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Sep 14, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
belikor
added a commit
to belikor/lbry-sdk
that referenced
this issue
Sep 19, 2021
As reported in issue lbryio#2769, the `lbrynet` daemon doesn't respond correctly when it is compiled against Python 3.8+, only with Python 3.7. Instead of using `aiohttp==3.5.4` which was released on January 12, 2019, we use `aiohttp=3.6.2` which was released October 9, 2019, and is available in Ubuntu 20.04. By using this newer version, the RCP server seems to work correctly both with Python 3.8 and 3.9. We could also try a newer version, like `3.7.4` as it was launched on February 25, 2021, and is available in Arch.
|
This issue has been solved. I installed it in a venv running Python version 3.9.9 and everything worked just fine. Out of interest I also (not at the same time) removed all of the required version numbers in |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After some testing and some discussion with @er013 it's apparent that there's some kind of silent incompatibility with Python
3.8.xthat'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
lbrynetversion (0.58.1) is installed with Python3.7.6the API will respond successfully:The text was updated successfully, but these errors were encountered: