https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112013-04-19T15:49:23ZRuby Issue Tracking SystemRuby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=387382013-04-19T15:49:23Zhalorgium (Tim Carey-Smith)ruby@spork.in
<ul></ul><p>Should this be in common-ruby?<br>
Could someone move it?</p> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=387422013-04-19T16:34:18Ztmm1 (Aman Karmani)ruby@tmm1.net
<ul><li><strong>Project</strong> changed from <i>Ruby master</i> to <i>14</i></li></ul> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=387452013-04-19T19:55:02Zhalorgium (Tim Carey-Smith)ruby@spork.in
<ul></ul><p>There was some confusion about what I am proposing.<br>
I realised I didn't even explain this!</p>
<p>I would like to be able to see the backtrace of individual Fibers.<br>
This would allow our Celluloid.stack_dump to show each point at which the Fibers are waiting.</p> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=387822013-04-20T20:36:44Zhalorgium (Tim Carey-Smith)ruby@spork.in
<ul></ul><p>I have implemented Fiber#backtrace in Rubinius and have a demo of what I wanted to achieve.</p>
<p><a href="https://gist.github.com/halorgium/c770d3cf27f6279e5e43" class="external">https://gist.github.com/halorgium/c770d3cf27f6279e5e43</a></p>
<p>This depends on another change, Thread#root_fiber, which returns the root_fiber of the specified Thread.</p> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=389712013-04-28T07:53:30Zko1 (Koichi Sasada)
<ul><li><strong>Assignee</strong> set to <i>ko1 (Koichi Sasada)</i></li></ul><p>Sorry, I can't understand what is your proposal.</p>
<p>At first example <a href="https://gist.github.com/halorgium/f63abf177a96d7113ce3" class="external">https://gist.github.com/halorgium/f63abf177a96d7113ce3</a>,<br>
there is only "thread.backtrace". However, we have already Thread#backtrace.</p>
<p>p Thread.current.backtrace<br>
#=><br>
ruby 2.1.0dev (2013-03-18 trunk 39808) [i386-mswin32_100]<br>
["t.rb:2:in <code>backtrace'", "t.rb:2:in </code>'"]</p>
<hr>
<p>BTW, please add more specific description.</p>
<p>For example, Rdoc style description for proposed methods<br>
is very welcome because we can understand your proposal<br>
and we (especially I, who is not good English writer)<br>
can copy this document to implemented source code!</p> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=389922013-04-28T19:30:02Zhalorgium (Tim Carey-Smith)ruby@spork.in
<ul></ul><p>When you have many Fibers inside a Thread.<br>
You cannot find where the FIbers are currently suspended.</p>
<p>I propose adding a method to Fiber to return this information.</p>
<p>Calling Fiber.current.backtrace would be equivalent to Thread.current.backtrace due to the nature of Fibers.</p>
<p>Does this help with understanding?</p> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=628762017-02-06T02:58:19Zko1 (Koichi Sasada)
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/62876/diff?detail_id=43895">diff</a>)</li></ul><p>It seems nice.</p> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=642662017-04-17T05:36:39Zshyouhei (Shyouhei Urabe)shyouhei@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li></ul> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=702702018-02-08T09:51:39Zgooglefeud (google feud (spammer, locked))
<ul><li><strong>Subject</strong> changed from <i>Support discovering yield state of individual Fibers</i> to <i>google gravity </i></li></ul><p>You can solve your issue by using <a href="http://www-googlegravity.com/" class="external">anti google gravity underwater</a></p> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=702732018-02-08T10:01:26Zusa (Usaku NAKAMURA)usa@garbagecollect.jp
<ul><li><strong>Subject</strong> changed from <i>google gravity </i> to <i>Support discovering yield state of individual Fibers</i></li></ul> Ruby master - Feature #8263: Support discovering yield state of individual Fibershttps://redmine.ruby-lang.org/issues/8263?journal_id=955302021-12-23T23:40:34Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul><li><strong>Project</strong> changed from <i>14</i> to <i>Ruby master</i></li></ul>