quic: fix wake up blob

The quic implementation calls setWakeUp with
the assumption, that it is only executed once
per event loop cycle.
This assumption is wrong.
Only setImmediate will guarantee, that the
execution is delayed to later in the event loop
and happening once in the event loop.

Fixes: #64035
Signed-off-by: Marten Richter <marten.richter@freenet.de>
PR-URL: #64044
Reviewed-By: James M Snell <jasnell@gmail.com>

Author: martenrichter

lib/internal/blob.js

@@ -469,9 +469,13 @@ function createBlobReaderStream(reader) {
       this.pendingPulls = [];
       // Lazily register a wakeup callback that the C++ side can invoke
       // when new data is available after a STATUS_BLOCK.
+      let immediate;
       this.wakeup = () => {
         if (this.pendingPulls.length > 0) {
-          this.readNext(c);
+          immediate ??= setImmediate(() => {
+            immediate = undefined;
+            this.readNext(c);
+          });
         }
       };
     },
@@ -571,7 +575,15 @@ const kMaxBatchChunks = 16;
 async function* createBlobReaderIterable(reader, options = {}) {
   const { getReadError } = options;
   let wakeup = PromiseWithResolvers();
-  reader.setWakeup(wakeup.resolve);
+  let immediate;
+  let fin = false;
+  reader.setWakeup((setfin) => {
+    fin ||= setfin;
+    immediate ??= setImmediate(() => {
+      immediate = undefined;
+      wakeup.resolve?.();
+    });
+  });
 
   try {
     while (true) {
@@ -616,9 +628,8 @@ async function* createBlobReaderIterable(reader, options = {}) {
       if (error) throw error;
 
       if (blocked) {
-        const fin = await wakeup.promise;
+        await wakeup.promise;
         wakeup = PromiseWithResolvers();
-        reader.setWakeup(wakeup.resolve);
         // If the wakeup was triggered by FIN (EndReadable), the DataQueue
         // is capped. Continue the loop to pull again -- the next pull will
         // return EOS. Without this, a race between the data notification