Fix float("inf") timeouts#846
Conversation
91746b0 to
0fe61f0
Compare
This means that we would not support pool timeout, which I believe is critical. Also, look at #814. The previous behavior was very unstable and unpredictable. |
|
So... We have a stable version with a minor issue that some timeouts can take longer than expected in some circumstances. My strong preference in a case like that is to immediately roll back the change, re-release, and then make sure we're slowing down on future changes. I'm up for re-reviewing #822 and #823 (plus this change) but I'd much rather be able to do that in a way that's not time-pressured. |
|
It's up to you.
I would agree if the issue was not small enough to be fixed immediately in the next release. |
lovelydinosaur
left a comment
There was a problem hiding this comment.
👍 Okay, yep. You've probs got a good call on this one.
Would you also like to roll up a 1.0.2 release for this?
(thanks)
Yes I would |
Resolves #845
The issue is that our
AsyncEvent.waitsupportsfloat('inf')timeout butEvent.waitdoesn't.Simple demonstration:
Works
Doesn't work
Error: