[Bug]: protocol.handle unexpected behavior when request.body is a ReadableStream

[thecodrr]

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version

26.1.0

What operating system are you using?

Windows

Operating System Version

Windows 11 22H2

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

Iterating on a ReadableStream inside protocol.handle should not output anything except what is fed into the stream.

Actual Behavior

Currently, doing this outputs a bunch of undefined entries when it shouldn't

protocol.handle(SCHEME, async (request) => {
  console.log("starting stream");
  for await (const p of request.body) {
    console.log(p);
  }
  console.log("ending stream");
});

For some reason, the first few logs are correct outputting Uint8Array as expected but it eventually starts outputting undefined:

starting stream
Uint8Array(5) [ 84, 104, 105, 115, 32 ]
Uint8Array(3) [ 105, 115, 32 ]
Uint8Array(2) [ 97, 32 ]
Uint8Array(5) [ 115, 108, 111, 119, 32 ]
Uint8Array(8) [
  114, 101, 113,
  117, 101, 115,
  116,  46
]
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
ending stream

The main problem is that such a ReadableStream is not accepted by net.fetch or fetch and they crash with the following error:

node:52760) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be of type string or an instance of Buffer or Uint8Array. Received undefined
    at new NodeError (node:internal/errors:399:5)
    at _write (node:internal/streams/writable:315:13)
    at ClientRequest.write (node:internal/streams/writable:337:10)
    at Object.write (node:internal/webstreams/adapters:179:63)
    at ensureIsPromise (node:internal/webstreams/util:192:19)
    at writableStreamDefaultControllerProcessWrite (node:internal/webstreams/writablestream:1115:5)
    at writableStreamDefaultControllerAdvanceQueueIfNeeded (node:internal/webstreams/writablestream:1230:5)
    at writableStreamDefaultControllerWrite (node:internal/webstreams/writablestream:1104:3)
    at writableStreamDefaultWriterWrite (node:internal/webstreams/writablestream:994:3)
    at [kChunk] (node:internal/webstreams/readablestream:1399:28)
(Use `Notesnook --trace-warnings ...` to show where the warning was created)
(node:52760) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)

On the browser side, I am doing a simple fetch like so:

  function wait(milliseconds: number) {
    return new Promise((resolve) => setTimeout(resolve, milliseconds));
  }

  const stream = new ReadableStream({
    async start(controller) {
      await wait(1000);
      controller.enqueue("This ");
      await wait(1000);
      controller.enqueue("is ");
      await wait(1000);
      controller.enqueue("a ");
      await wait(1000);
      controller.enqueue("slow ");
      await wait(1000);
      controller.enqueue("request.");
      controller.close();
    }
  }).pipeThrough(new TextEncoderStream());

const response = await fetch(uploadUrl, {
    method: "PUT",
    body: stream,
    signal,
    duplex: "half"
  });

Testcase Gist URL

https://gist.github.com/thecodrr/ddabb97be1e93435f9e25dcfab76876e

Additional Information

No response