Oleg Sukhodolsky
Oleg Sukhodolsky
I'm not sure about @deivid-rodriguez but I usually use debug output :) As for the problem I suspect the call tries to perform some operation on some dedicated thread which...
> Thanks! By "debug output" do you mean just printing to the terminal using puts or pp? yep. Verbose mode is useful but may be too noisy.
It looks like we see enumerator's implementation details: it replace whole call stack. But all four debugging gems I know (byebug, debugger, debase, and ruby-debug-base) are written in assumption that...
As far as I can see Enumarator#next uses fiber (https://github.com/ruby/ruby/blob/trunk/enumerator.c#L610) which in turn does all dirty hacks (e.g. see https://github.com/ruby/ruby/blob/trunk/cont.c#L1337)
Here is the test ``` ruby fiber = Fiber.new do number = 0 count = 1 loop do number += count count += 1 Fiber.yield number end end puts fiber.resume...
I've performed more tests and it looks like we receive no events for creation/switching of Fibers :( Imho we need them but it also mean that we will need to...
As soon as we both agree that it looks like a reasonable API, I will file the issue there and link it to this one.
https://bugs.ruby-lang.org/issues/11348 created
It looks like ExoPlayer's bug has been fixed Jan 19, 2019. Time to close this one?
Hi @astashov :) we do interested (new Rails add byebug to Gemfile by default (we have not found any problem yet but I'd expect to have some). As for implementation...