asynchronous

It seems to me that if you have a wrapper function
https://github.com/libuv/libuv/blob/a39009a5a9252a566ca0704d02df8dabc4ce328f/test/runner-unix.c#L45
for close, then in this places you can use it.
https://github.com/libuv/libuv/blob/a39009a5a9252a566ca0704d02df8dabc4ce328f/test/runner-unix.c#L336
https://github.com/libuv/libuv/blob/a39009a5a9252a566ca0704d02df8dabc4ce328f/test/runner-unix.c#

Right now, whenever Zenmap crashes, it gives the user a stack trace and asks the user to send it to the Nmap dev list. So we get a flood of emails (most of which aren't even allowed through moderation) which often contain just a stack trace with no subject line or any explanatory text in the message body. Lots of these are for well known issues in older versions of Zenmap. So it's not very usef

As of now FluxGoupeBy dropping elements silently #2352 so the related tests case may be unstable (https://github.com/reactor/reactor-core/runs/3054668530?check_suite_focus=true#step:5:516).

One suggestion to improve it is to add .doOnDiscard(Long.class, downstream::addAndGet) to improve its stability

We have utf8Decode but not utf8Encode, etc.

Replace concrete Bastion Executor with Agnostik.
So everyone can use whatever they want as guarantee.