From 1c7d10eea1bb34d353230c877781a534a47fee5b Mon Sep 17 00:00:00 2001
From: Patrik Oldsberg <poldsberg@gmail.com>
Date: Thu, 31 Oct 2024 11:14:47 +0100
Subject: [PATCH] events-node: more reliable way to wait for 202 body to close

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
---
 plugins/events-node/src/api/DefaultEventsService.ts | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/plugins/events-node/src/api/DefaultEventsService.ts b/plugins/events-node/src/api/DefaultEventsService.ts
index caafe50d8f..7a35ed305a 100644
--- a/plugins/events-node/src/api/DefaultEventsService.ts
+++ b/plugins/events-node/src/api/DefaultEventsService.ts
@@ -214,7 +214,10 @@ class PluginEventsService implements EventsService {
             // immediately again
 
             lock.release();
-            await res.body?.getReader()?.closed;
+            // We don't actually expect any response body here, but waiting for
+            // an empty body to be returned has been more reliable that waiting
+            // for the response body stream to close.
+            await res.text();
           } else if (res.status === 200) {
             const data = await res.json();
             if (data) {