See original issue and associated discussion in Node.js issue tracker here: nodejs/node#36158

/cc @asklar, @aduh95, @bzoz

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

Following test failng with scala 2.13.5:

https://github.com/zio/zio/blob/e94be1899eddf43923c979eec2dae78bdd936281/test-junit-tests/jvm/src/test/scala/zio/test/junit/MavenJunitSpec.scala#L17

Error

[info] - MavenJunitSpec
[info]   - FailingSpec results are properly reported
[info]     Fiber failed.
[info]     A checked error was not handled.
[info]     java.io.FileNotFoundExce

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