Hi, thanks for all your great work, Ruby crew! I have a test in my project that uses `ObjectSpace.each_object(Fiber).count` to see how many Fibers have been started by my code. This test started failing when I added other tests using ...rmosolgo (Robert Mosolgo)
That definitely makes sense for a Fiber killing _itself_, but would you say that killing a _different_ Fiber should cause a fiber to transfer away? In my first script above, calling `worker.kill` causes the `manager` fiber to transfer. ...rmosolgo (Robert Mosolgo)
Thanks for taking a look! I was going from the example in the docs (https://docs.ruby-lang.org/en/master/Fiber.html#method-i-transfer), where the return value of `.transfer` is used by the caller. And `.transfer` _does_ return to the...rmosolgo (Robert Mosolgo)
I was hoping to use `Fiber#kill` to clean up formerly `.transfer`-d Fibers and work around https://bugs.ruby-lang.org/issues/20081, but I found that `Fiber#kill` has a similar control flow jump behavior. Is this on purpose, or a bug? ...rmosolgo (Robert Mosolgo)
I see that Ruby 3.3 has `Fiber#kill` coming (https://github.com/ruby/ruby/pull/7823), which I _think_ will solve my problem: I can manually `.kill` Fibers instead of running them until they return. But still, I'm interested to learn whet...rmosolgo (Robert Mosolgo)
Hi! I'm trying to figure out how to make sure that Fibers started with `.transfer` end up _terminated_, not just suspended. (If they're suspended, Rails thinks they're still alive, and they continue to hold onto database connections, see...rmosolgo (Robert Mosolgo)
Hi! I'm trying to improve my Ruby library to support transfer-based fibers (https://github.com/rmosolgo/graphql-ruby/pull/4322). To test parallel I/O, I'm using `system("sleep #{duration}")`, but this causes a segfault sometimes. I'd lov...rmosolgo (Robert Mosolgo)
I heard someone ran into this error in a GraphQL-Ruby context, so I thought I'd check out this script on the latest Ruby. It didn't crash as-written, so I added a couple more orders of magnitude. It still finished fine locally, but slowe...rmosolgo (Robert Mosolgo)
Oh, thanks! I installed 3.1.0-dev and it worked fine for me, too. (That is, it failed with a nice error message and backtrace.) I thought I was on the latest version, but I guess I overlooked the `-dev` version. I can't figure out how ...rmosolgo (Robert Mosolgo)
Ah, yes, thanks for linking back to that. It sure looks like the same thing. I searched for "fiber scheduler segfault" and didn't find it, but I see it calls it "segv" instead. Please feel free to close this one if it's not useful (I...rmosolgo (Robert Mosolgo)
rmosolgo (Robert Mosolgo)03:29 PM Ruby Bug #21401 (Rejected): ObjectSpace can't count Fibers after using a Ractor