Closed christopherfujino closed 11 months ago
Here's the line: https://github.com/FormerLurker/Octolapse/blob/8d53c91069943b9b4d78498c2fc225b3d6d04cb8/octoprint_octolapse/camera.py#LL209C18-L209C18
thread.join(requests.packages.urllib3.util.retry.Retry.BACKOFF_MAX)
It appears I have version of requests
v2.31.0 -> urllib3
v2.0.3.
It looks like package urllib3 got rid of the urllib3.util.retry.Retry.BACKOFF_MAX
static in https://github.com/urllib3/urllib3/commit/f69b1c89f885a74429cabdee2673e030b35979f0, allowing it to be configurable. One possible fix here (assuming all clients are using a new enough version of urllib3) would be to use requests.packages.urllib3.util.retry.Retry.DEFAULT_BACKOFF_MAX
. Although maybe hard-coding our own value would be safer, and not be broken by upstream changes.
FYI @beepboop1234
FYI @beepboop1234
Thanks! It looks like you are seeing all of the same errors I am. If I can give any info or do any testing that would help fix this, just let me know.
I noticed any changes I make seem to stick despite the errors so I've just been dismissing the pop-ups. Would love to not get the errors though.
I'm a complete noob, but know just enough to get in trouble. I found the camera.py file and changed the line from thread.join(requests.packages.urllib3.util.retry.Retry.BACKOFF_MAX) to thread.join(requests.packages.urllib3.util.retry.Retry.DEFAULT_BACKOFF_MAX)
and that seemed to do the trick
I'm a complete noob, but know just enough to get in trouble. I found the camera.py file and changed the line from thread.join(requests.packages.urllib3.util.retry.Retry.BACKOFF_MAX) to thread.join(requests.packages.urllib3.util.retry.Retry.DEFAULT_BACKOFF_MAX)
and that seemed to do the trick
I think we can close this since https://github.com/FormerLurker/Octolapse/pull/913/files was merged
Version of Octolapse
Octolapse Version: v0.4.3
OctoPrint Version: 1.9.0
When you ran into the problem, did you have diagnostic logging enabled?
Diagnostic Logging was Enabled: yes
What were you doing when the problem occurred
What should have happened?
Settings should have been saved (since no changes made, effectively nothing)
What happened instead?
An error alert pops up:
Operating System running OctoPrint and Octolapse
OS Name: Octopi Os Version: 0.18.0
Link to plugin_octolapse.log
Link to plugin_octolapse.log:
(This doesn't look particularly interesting, see instead octoprint.log)
Link to octoprint.log
This is I believe the real error:
octoprint.log:
Note this was already filed upstream on octoprint 3 weeks ago, but closed: https://github.com/OctoPrint/OctoPrint/issues/4811