@Sean - as with any race bugs with eventlet, the reproducer is not that straightforward - it would require threads for specific requests in the scheduler switching at the right time. However from just simple code inspection - it's clear that the scheduler was designed to be "racy" - this is a design choice afaict.
@Sean - as with any race bugs with eventlet, the reproducer is not that straightforward - it would require threads for specific requests in the scheduler switching at the right time. However from just simple code inspection - it's clear that the scheduler was designed to be "racy" - this is a design choice afaict.