inspector: response.setEncoding() causes response.on('data') never triggered when --experimental-network-inspection is enabled

Version

v24.17.0

Platform

Windows 11 x64 (10.0.26200)

Subsystem

No response

What steps will reproduce the bug?

When experimental network inspection is enabled, calling response.setEncoding() on an http.IncomingMessage causes Node Inspector to throw exception.
The exception interrupts normal stream processing. response.on("data") callback never triggered.

const http = require('http');

http.get("http://example.com", (response) => {
    response.setEncoding("utf8");

    response.on("data", chunk => {
        console.log(chunk);
    });

    response.on("end", () => {
        console.log("end");
        process.exit(0);
    });

});

Run node --inspect --experimental-network-inspection main.js then open any inspector frontend (Chrome DevTools).

How often does it reproduce? Is there a required condition?

When network inspection feature enabled.

What is the expected behavior? Why is that the expected behavior?

Network inspection should continue to work regardless of whether response.setEncoding() is used.

What do you see instead?

Nodejs throws exception and interrupts normal stream processing. response.on("data") callback never triggered.

Additional information

VSCode extension debugging host enables this feature and breaks my extension development. Waste 2 days to find out why every http request got empty response.

首先使用 node --inspect --experimental-network-inspection main.js 和 inspector frontend 运行提供的 HTTP 示例，然后捕获由 response.setEncoding() 触发的异常。跟踪中断流的网络检查处理；当启用编码后，data 和 end 回调能够正常运行时，即表示完成。