Release v19.113.2

observers.subscriberTimeout had no effect above clustering.responseTimeout (30 s by default). The subscriber call is an Orleans grain call, so Orleans gave up first, and the kernel then reported that as "did not answer within ".

Changed

• IObserverSubscriber.OnNext, IObserverPageSubscriber.OnNextPage and the webhook OnNext overload now have their own Orleans response timeout of 1 hour (ObserverSubscriberResponseTimeout). observers.subscriberTimeout is now the deadline that fires; it is no longer capped by clustering.responseTimeout. The attribute is not part of the method's wire identity, so OrleansContracts.txt is unchanged and rolling upgrades are unaffected. (#5440)
• When Orleans itself gives up on a subscriber call, it is reported as SubscriberResponseTimedOut with the elapsed time and the ceiling, instead of as the configured subscriber timeout. It still classifies as FailureKind.Timeout.
• The kernel logs a warning at startup when observers.subscriberTimeout is 0 or above the 1-hour ceiling.
• Documented how subscriberTimeout relates to clustering.responseTimeout.