Bruno Sutic

Hi, I think you only need to have `bash` installed on the system. `bash` does not need to be the default shell.

Hi, what you guys are doing is bleeding edge work. I'm pretty sure no serious app/gem is using raw fiber scheduler interface - yet... About the `yield`/`resume` vs `#transfer` approach:...

All of this is hard work and a lot of research.

I chatted with @dbackeus about the problem you're describing. I understand it as the following: - Run a main fiber (GraphQL execution). - Spawn multiple fibers that do some network...

Quick update: I'm aware of `/set plugins.var.python.notification_center.ignore_current_buffer_messages "on"`. It doesn't help the above scenario if I quickly navigate to check another buffer and the person I'm actively messaging sends the...

> Hanging on swallowed error Well, the error is not really "swallowed" or suppressed. Inside an `Async` block `sleep` is handled by an `Async::Scheduler#kernel_sleep` fiber scheduler method. The implementation for...

I could be wrong, but I think this is not considered a bug. I'm sure you could find more "minor gotchas" like this with other blocking methods that delegate to...

Here are the docs: https://docs.ruby-lang.org/en/3.1/Fiber/SchedulerInterface.html

From #62: > The idea of a barrier is that it's stateful, you can call wait(2) several times until it's exhausted. Does the current implementation enable this feature? Since `@done`...

Hey, yea, I can see how this bug could happen. I never used this plugin in these scenarios.. it was designed for more "static" environment. The readme is explicit about...