Resets and non-pipeline requests were not triggering the connection receive timeout.
The problem happened because of the timeout mechanics only started when pending observers are set.
However, the current observer should be also be considered for this use case.
Resets and non-pipeline requests were not triggering the connection receive timeout. The problem happened because of the timeout mechanics only started when pending observers are set. However, the current observer should be also be considered for this use case.