See: https://illumos.org/man/5/epoll

Idea: move logic from src/unix/linux-core.c to src/unix/epoll.c and share that between Linux and Illumos.

Motivation:

• removes 250-300 lines of code from src/unix/sunos.c
• switches to much more battle-hardened code
• makes libuv more efficient because it no longer has to accommodate this event ports quirk:

diff --git a/src/unix/core.c b/s

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

The window operators should indicate if the returned Flux for each window is safe to subscribe to multiple times.

Documentation Issue

I had a data processing pipeline that I introduced batching to, using the window operator. In this pipeline, it will retry a batch if it faces a transient error. When batching was added, and it retried, I saw a failure of `IllegalStateException: UnicastP

I have a small piece of zlayer code. The layers are defined as vals, like so:

  private final val kafkaLayer: Layer[Error, Kafka]                                      = Config.live >>> Kafka.live
  private final val transactorLayer: Layer[Error, DbTransactor]                          = (Blocking.live ++ ConfigDb.live) >>> db.hikariLayer
  private final val queryConfigLayer: Layer[

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