Ruby Issue Tracking System

04/28/2013

07:35 PM Ruby Feature #8291: Allow retrieving the root Fiber of a Thread

I am proposing adding the ability to call Thread#root_fiber to return the Fiber which is considered the original co-routine for the specified Thread.
This is useful to be able to retrieve information about the original Fiber for the Th... halorgium (Tim Carey-Smith)

07:30 PM Ruby Feature #8263: Support discovering yield state of individual Fibers

When you have many Fibers inside a Thread.
You cannot find where the FIbers are currently suspended.
I propose adding a method to Fiber to return this information.
Calling Fiber.current.backtrace would be equivalent to Thread.c... halorgium (Tim Carey-Smith)

04/20/2013

08:36 PM Ruby Feature #8263: Support discovering yield state of individual Fibers

I have implemented Fiber#backtrace in Rubinius and have a demo of what I wanted to achieve.
https://gist.github.com/halorgium/c770d3cf27f6279e5e43
This depends on another change, Thread#root_fiber, which returns the root_fiber of ... halorgium (Tim Carey-Smith)

04/19/2013

07:55 PM Ruby Feature #8263: Support discovering yield state of individual Fibers

There was some confusion about what I am proposing.
I realised I didn't even explain this!
I would like to be able to see the backtrace of individual Fibers.
This would allow our Celluloid.stack_dump to show each point at which th... halorgium (Tim Carey-Smith)

03:49 PM Ruby Feature #8263: Support discovering yield state of individual Fibers

Should this be in common-ruby?
Could someone move it? halorgium (Tim Carey-Smith)

03:53 PM Ruby Feature #8291 (Open): Allow retrieving the root Fiber of a Thread

=begin
Currently (({Thread.backtrace})) returns the stack frames for the currently running (({Fiber})).
It is not possible to retrieve the backtrace.
Building on http://bugs.ruby-lang.org/issues/8263, this would allow for this fea... halorgium (Tim Carey-Smith)

03:50 PM Ruby Feature #8215: Support accessing Fiber-locals and backtraces for a Fiber

I realised that this might be better in common-ruby.
I originally proposed the idea with RBX.
Could someone move it? halorgium (Tim Carey-Smith)

04/13/2013

11:18 AM Ruby Feature #8263 (Assigned): Support discovering yield state of individual Fibers

Related to #8215, when debugging a multi-Fiber application or library it is useful to be able to look at the stack for the `Thread` which is possible right now.
Currently it is not possible to discover where the Fiber was yielded.
... halorgium (Tim Carey-Smith)

04/07/2013

07:13 PM Ruby Feature #8215: Support accessing Fiber-locals and backtraces for a Fiber

Yup, I am sorry if that was not clear!
I also am very interested in being able to get the backtrace of a `Fiber` too.
Should I open a new issue for `Fiber#backtrace`?
halorgium (Tim Carey-Smith)

04/04/2013

08:47 AM Ruby Feature #8215 (Closed): Support accessing Fiber-locals and backtraces for a Fiber

=begin
As part of debugging celluloid, I have been wanting to diagnose where the Fibers are running and their various locals.
I would expect the following to work.
Thread.current[:key] = "outside"
fiber = Fiber.new do
Th... halorgium (Tim Carey-Smith)