STASIdownunder has quit [Read error: Connection reset by peer]
gemmaro has quit [Ping timeout: 260 seconds]
gemmaro_ has joined #ruby
STASIdownunder has joined #ruby
rhe has quit [Quit: Ping timeout (120 seconds)]
rhe has joined #ruby
<nakilon>
I wish there was a way to know that the binding.irb was called; so I could stop printing things in another looped thread
<nakilon>
I could assign the thread to some global variable and kill it before binding.irb though
<nakilon>
but maybe there is a way to know if there is a some kind of terminal session active in any thread that waits for user input (i.e. irb session)
STASIdownunder has quit [Read error: Connection reset by peer]
Rounin has joined #ruby
<nakilon>
should I store my Thread via "config.add_setting :my_thread" or via "before(:all){ @my_thread = ... }"?
otisolsen70 has joined #ruby
STASIdownunder has joined #ruby
nirvdrum741 has quit [Remote host closed the connection]
<nakilon>
are the only differences between shared contexts (config.include_context) and modules (config.include) these? 1. module can also be used with "config.extend" 2. module can't include contexts/examples
nirvdrum741 has joined #ruby
STASIdownunder has quit [Read error: Connection reset by peer]
infinityfye has quit [Read error: Connection reset by peer]
<havenwood>
nakilon: It might be worth swapping `Time.now` for `Process.clock_gettime(Process::CLOCK_MONOTONIC)` for monotonic time so edge cases like time adjustments or daylight saving don't occasionally make the test fail.
hwpplayer1 has joined #ruby
hwpplayer1 has quit [Ping timeout: 244 seconds]
schne1der has quit [Ping timeout: 276 seconds]
trillion_exabyte has joined #ruby
user71 has quit [Quit: Leaving]
___nick___ has quit [Ping timeout: 248 seconds]
schne1der has joined #ruby
<nakilon>
so I backtracked the infinite loop until found it's not a third-party library bug but a loop in my code; I think I need some sort of profiling, but it should better be a line profiler; and it should count the calls, so when you are stuck in the loop there is a clear border in the backtrace where the counter would grow
<nakilon>
probably it's done via TracePoint
andy-turner has quit [Quit: Leaving]
schne1der has quit [Ping timeout: 248 seconds]
<o0x1eef>
Sounds similar to: https://github.com/0x1eef/trip.rb?tab=readme-ov-file#require - where I count the number of requires Pry makes. It is built on TracePoint. It might save you some time. Otherwise vanilla TracePoint can definitely do that, but probably with a bit of code.
cappy has joined #ruby
hwpplayer1 has joined #ruby
ruby[bot] has quit [Remote host closed the connection]