Handle the out of Memory error by counting subsequent timeouts - keep alive - Implement ConnectionError #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello OnFreund,
i tested a few things regarding the "out of Memory error" home-assistant/core#119138 over the last weeks, just right before you updated your repository -- in fact i came a bit late with this now :)
I don´t know if my changes would fit your standard. But in fact it solves the problem with out of memory in my case compleatly.
(i´m using pyrisco with HomeAssistant in local) !
--> If a "Timeout CLOCK" happens 3 times subseqently, i´m raising an error "ConnectionError"
In my test together with HomeAssistant Integration i checking for the error the same way you do for "ConnectionResetError" (init_.py) and starting a reload of the Integration when "ConnectionError" is raised by pyrisco.
I would be happy if you can take parts of my changes for everyone´s needs.
Best regards
Jakob