{"push_id":607088478,"size":1,"distinct_size":1,"ref":"refs/heads/bounded-resources","head":"eb33e452f62ab84a834f8b077548ba49d35b6512","before":"8a0deeb8b77d8b7414928e49ceb608c4ad0453a0","commits":[{"sha":"eb33e452f62ab84a834f8b077548ba49d35b6512","author":{"email":"bfc4a29df8a83bf0d0b972ff8d7124c864f353ce@gmail.com","name":"mouad.benchchaoui@deliveryhero.com"},"message":"Add enability to bound greenlets pool from configuration\n\nAdd a NonBlockingPool that in contrast of gevent.pool.Pool it's non blocking and\nas soon as pool limit are reached it will reject work instead of blocking, which\ncan be very dangerous when you can block for ever and with it block calling greeenlet\nin other services ... .\n\nWhen Pool reject jobs it raise a ``ResourceExhausted`` subclass, the idea is to expose\nthis exception and then add a back pressure support with bulkhead pattern into client\nfor more resilience.\n\nThe NonBlockingPool is also used in gevent WSGI server to bound resources.","distinct":true,"url":"https://api.github.com/repos/mouadino/lymph/commits/eb33e452f62ab84a834f8b077548ba49d35b6512"}]}