Windows

following up the discussion in nodejs/node#43757
if we want to allow the concurrency option to be a boolean, we need to come up with good defaults

there are two levels of concurrency:

1. when running multiple test files, using --test each file is spawned in its own process so we use os.cpus().length as the default
2. inside a test file - we use 1 as the default

Feature type

Plug-ins

Describe the feature

Is it possible to fix the data wrapper plugin for asm-style, The current version like this

array DB 4Dh, 5Ah, 90h, 00h, 03h, 00h, 00h, 00h, 04h, 00h, 00h, 00h, 0FFh, 0FFh, 00h, 00h,
              0B8h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 40h, 00h, 00h, 00h, 00h, 00h, 00h, 00h,
              00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h

caddy.zip

• 运行压缩包内的caddy.exe
• 得到PAC地址,可以填入IE中 http://127.0.0.1:10810/pac

压缩包内的pac文件中,下面字符串可以自行修改,连接的是本地的http端口10809
var proxy = "PROXY 127.0.0.1:10809;";

What's the Problem?

No response

Solution/Idea

Alternatives

NA

Priorities

It may be a specific request but since there is a zip file handler for Android, doesn't hurt to ask for a desktop (maybe multiple backends?) implementation.

I would like to try that in the future but if anyone has time before feel free to do it.

Similar

Refs: nodejs/node#43931

Libuv either:

1. Posts a "give me a datagram" IOCP request, or
2. Queues up a "zero read" to get notified when new datagrams come in

It should be possible in both cases to call WSARecvFrom() a few times to receive more pending datagrams. There should be a limit to avoid denial-of-service attacks. src/unix/udp.c limits it to 32 datagram