Dave Protasowski
Dave Protasowski
> I think we should not scale down if activator is not in the path right (when desiredScale is 0), @dprotaso wdyth? Yeah I agree
I think we should update the PR so that we are only marking `ActivatorEndpointsPopulated` when we are actually wiring the activator in the data path with ready endpoints.
Also thanks for the investigation everyone - it helped me be more informed on the path to take here.
hey @yenniechen just following up
/hold we shouldn't be duplciating work https://github.com/knative/serving/issues/15007#issuecomment-2173124094
/ok-to-test
@nkreiger - hi - can you just confirm my understanding reading the above discussion Essentially the setting `revision-response-start-timeout-seconds` is not behaving accurately in the activator and pre-maturely terminating http requests?
Also note by setting `revision-response-start-timeout-seconds` you app needs to write _something_ on the wire before that timeout
I confirmed an odd behaviour ``` max-revision-timeout-seconds: "40" revision-idle-timeout-seconds: "0" revision-response-start-timeout-seconds: "10" revision-timeout-seconds: "30" ``` We have a test image here: https://github.com/knative/serving/tree/main/test/test_images/timeout I would expect the following to succeed -...