<div dir="ltr"><div>Hello,</div><div><br></div><div>Thanks for the heads up.</div><div><br></div><div>You are right this is related to <a href="https://bugs.python.org/issue20319">https://bugs.python.org/issue20319</a></div><div>futurist implement a similar code than the cpython concurrent.future code but not fixed yet.</div><div><br></div><div><div>I just submitted a patch to fix that, feel free to review it:</div><div>- <a href="https://review.opendev.org/689691">https://review.opendev.org/689691</a></div><div><br></div><div>Thanks<br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le sam. 19 oct. 2019 à 08:44, <a href="mailto:info@dantalion.nl">info@dantalion.nl</a> <<a href="mailto:info@dantalion.nl">info@dantalion.nl</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello everyone,<br>
<br>
I think I have found a significant bug in the futurist concurrency<br>
library that is breaking for my application.<br>
<br>
If I launch a threadpool and submit n > 1 number of tasks. If now for<br>
any n of these tasks such a task calls Condition.wait(). Than when<br>
waiters.wait_for_any is called from the main thread it will block<br>
indefinitely instead of returning the n - 1 tasks that have completed.<br>
Furthermore setting the timeout parameter in wait_for_any is<br>
subsequently ignored.<br>
<br>
I have submitted this as a bug report on launchpad:<br>
<a href="https://bugs.launchpad.net/futurist/+bug/1848457" rel="noreferrer" target="_blank">https://bugs.launchpad.net/futurist/+bug/1848457</a><br>
<br>
Any help on this is really appreciated as I think it is a significant issue.<br>
<br>
Kind regards,<br>
Corne Lukken (Dantali0n)<br>
<br>
PS: I also submitted this over on stackoverflow:<br>
<a href="https://stackoverflow.com/questions/58410610/calling-condition-wait-inside-thread-causes-retrieval-of-any-future-to-block-o" rel="noreferrer" target="_blank">https://stackoverflow.com/questions/58410610/calling-condition-wait-inside-thread-causes-retrieval-of-any-future-to-block-o</a><br>
<br>
<br>
<br>
<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Hervé Beraud</div><div>Senior Software Engineer<br></div><div>Red Hat - Openstack Oslo</div><div>irc: hberaud</div><div>-----BEGIN PGP SIGNATURE-----<br><br>wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+<br>Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+<br>RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP<br>F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G<br>5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g<br>glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw<br>m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ<br>hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0<br>qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y<br>F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3<br>B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O<br>v6rDpkeNksZ9fFSyoY2o<br>=ECSj<br>-----END PGP SIGNATURE-----<br><br></div></div></div></div></div></div></div></div></div></div></div></div></div>