Samuel Williams

The other question is, should we have a timeout by default? It seems a bit silly to me that sockets can block code indefinitely.

I've released `async` v1.13.0 which changed the internal timeout API to raise the `Async::TimeoutError` exception and I'm preparing an update to `async-io` which includes a per-socket `timeout_duration`: https://github.com/socketry/async-io/blob/e9e7c268324002dc9e4db0f18a93bc4a0a26b38b/spec/async/io/socket_spec.rb#L87-L100 I'm not...

If you are doing high latency blocking operations in the event loop you will see this kind of response. Because the core of the event loop for the server is:...

That is a good question. Yes, hybrid mode should give you mostly the same performance characteristics as puma cluster mode. However, ideally you use non-blocking adapters otherwise there are still...

thanks for your report I will investigate.

Awesome, I will review it in the next day or two.

I will take a look.

If you have time to make a minimal repro within just Async and Concurrent ruby that would be awesome.

The 2nd issue reported is probably the same issue as https://github.com/socketry/async/issues/157

My understanding is the debug gem introduces autoload which can cause the described hang.