Subhi Al Hasan

try adding this.detector.detectChanges(); after each progress event

HI @mcollina I'd like to work on this one. Can you assign me to it?

@mcollina what is the reason behind introducing the balancedPool? Is it to support distributing the requests to multiple upstreams?

Do you already have an idea what the algorithm should do? I took a brief look into the paper; the algorithm that is used to decide the weights assumes that...

Hi guys, I finally have a vacation so hopefully I'll be able to wrap this thing 🙏 I was stuck at testing and currently working on rebasing after the new...

I've written a test runner part of the `balanced-pool.js` tests to be able to easily test the algorithm. Please note the results vary according to the starting weight per server...

I'm not sure wether we should have the errorPenalty and startingWeightPerServer as a configured value by the user or should we have a static one defined by us

@mcollina do we have an estimate about how many upstreams would probably be added? like a max of 100? I'm asking because currently the algorithm suffers from a case where...

I'm seeing a weird behaviour where I have 3 upstreams (A,B,C) and only 1 of them goes down C. After C is down upstreams A, B will also emit a...

my bad it seems related to the test server keepalive timeout configuration :(