Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Socket not closed properly #11

Open
freol35241 opened this issue Aug 20, 2023 · 1 comment
Open

Bug: Socket not closed properly #11

freol35241 opened this issue Aug 20, 2023 · 1 comment

Comments

@freol35241
Copy link

freol35241 commented Aug 20, 2023

I see the following type of warnings in the logs when using pyduro

WARNING py.warnings /usr/local/lib/python3.11/site-packages/pyduro/actions/set.py:45: ResourceWarning: unclosed <socket.socket fd=4, family=2, type=2, proto=0, laddr=('0.0.0.0', 1901)>

Which seems to relate to the fact that the socket that is created in Frame.send does not get properly closed. See: https://docs.python.org/3/library/socket.html#socket.socket.close

@victor987
Copy link

I get similar ones too:

WARNING py.warnings /usr/local/lib/python3.11/site-packages/pyduro/actions/raw.py:38: ResourceWarning: unclosed <socket.socket fd=4, family=2, type=2, proto=0, laddr=('0.0.0.0', 1901)>
response = frame.send(burner_address, verbose=verbose)
WARNING py.warnings /usr/local/lib/python3.11/site-packages/pyduro/actions/get.py:79: ResourceWarning: unclosed <socket.socket fd=4, family=2, type=2, proto=0, laddr=('0.0.0.0', 1901)>
response = frame.send(burner_address, verbose=verbose)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants