From 6b1c5e3d178944fcef149c458f4de6a1c7832766 Mon Sep 17 00:00:00 2001
From: Lee Rowlands <lee.rowlands@previousnext.com.au>
Date: Fri, 22 Jul 2022 06:47:24 +1000
Subject: [PATCH] Issue #3292980 by benjifisher, mikelutz, quietone: Testing
system should explain why Guzzle responses can be unreadable
---
core/tests/Drupal/Tests/BrowserHtmlDebugTrait.php | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/core/tests/Drupal/Tests/BrowserHtmlDebugTrait.php b/core/tests/Drupal/Tests/BrowserHtmlDebugTrait.php
index fe559499f55c..9ef1913ab609 100644
--- a/core/tests/Drupal/Tests/BrowserHtmlDebugTrait.php
+++ b/core/tests/Drupal/Tests/BrowserHtmlDebugTrait.php
@@ -182,7 +182,9 @@ protected function getResponseLogHandler() {
/** @var \Psr\Http\Message\StreamInterface $stream */
$stream = $response->getBody();
- // Get the response body as a string.
+ // Get the response body as a string. The response stream is set
+ // to the sink, which defaults to a readable temp stream but can
+ // be overridden by setting $options['sink'].
$body = $stream->isReadable()
? (string) $stream
: 'Response is not readable.';
--
GitLab