[oslo][futurist] Possible bug in futurist waiters.wait_for_any
Thanks for the heads up.
You are right this is related to https://bugs.python.org/issue20319
futurist implement a similar code than the cpython concurrent.future code
but not fixed yet.
I just submitted a patch to fix that, feel free to review it:
Le sam. 19 oct. 2019 Ã 08:44, info at dantalion.nl <info at dantalion.nl> a
> Hello everyone,
> I think I have found a significant bug in the futurist concurrency
> library that is breaking for my application.
> If I launch a threadpool and submit n > 1 number of tasks. If now for
> any n of these tasks such a task calls Condition.wait(). Than when
> waiters.wait_for_any is called from the main thread it will block
> indefinitely instead of returning the n - 1 tasks that have completed.
> Furthermore setting the timeout parameter in wait_for_any is
> subsequently ignored.
> I have submitted this as a bug report on launchpad:
> Any help on this is really appreciated as I think it is a significant
> Kind regards,
> Corne Lukken (Dantali0n)
> PS: I also submitted this over on stackoverflow:
Senior Software Engineer
Red Hat - Openstack Oslo
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...