On Wed, 2 Oct 2024 22:53:01 GMT, Jamil Nimeh wrote:
>> This PR corrects a flaw in the StatusResponseManager where it was
>> incorrectly swallowing the interrupt status when either an invokeAll was
>> called (spawning the threads to fetch each OCSP response) or when attempting
>> to grab the da
> This PR corrects a flaw in the StatusResponseManager where it was incorrectly
> swallowing the interrupt status when either an invokeAll was called (spawning
> the threads to fetch each OCSP response) or when attempting to grab the data
> from one of the Futures returned from the fetches.
> Ad
On Wed, 2 Oct 2024 21:44:08 GMT, Valerie Peng wrote:
>> This PR corrects a flaw in the StatusResponseManager where it was
>> incorrectly swallowing the interrupt status when either an invokeAll was
>> called (spawning the threads to fetch each OCSP response) or when attempting
>> to grab the d
On Fri, 27 Sep 2024 18:48:23 GMT, Jamil Nimeh wrote:
> This PR corrects a flaw in the StatusResponseManager where it was incorrectly
> swallowing the interrupt status when either an invokeAll was called (spawning
> the threads to fetch each OCSP response) or when attempting to grab the data
>
On Fri, 27 Sep 2024 18:48:23 GMT, Jamil Nimeh wrote:
> This PR corrects a flaw in the StatusResponseManager where it was incorrectly
> swallowing the interrupt status when either an invokeAll was called (spawning
> the threads to fetch each OCSP response) or when attempting to grab the data
>
This PR corrects a flaw in the StatusResponseManager where it was incorrectly
swallowing the interrupt status when either an invokeAll was called (spawning
the threads to fetch each OCSP response) or when attempting to grab the data
from one of the Futures returned from the fetches.
Additionally
