Xavier Noria

> But I would expect that only the traces registered by byebug itself are disabled, not all the traces registered by other libraries Exactly, I was wondering that too. I...

Ah! I forgot @palkan investigated this and left some comments in https://github.com/fxn/zeitwerk/issues/31#issuecomment-479996317.

This is a minimal reproduction that does not depend on Rails or Zeitwerk: ``` → tmp$ cat bar.rb class Bar end → tmp$ cat foo.rb TracePoint.new(:class) { |tp| p :CALLED...

@eregon if my memory does not fail me, it has to do with running things in different fibers /cc @gsamokovarov.

@gnachman oh, awesome! I'll do that. I was thinking also about detailing what is a font name exactly, because I had to try a bit for some. For example, for...

Was precisely looking into the code today. I think you're right.

I missed this one. If we replace `reload!` with a direct call to `Rails.autoloaders.main.reload`, the reload happens promptly. You cannot do that because reloading is not thread-safe, but that result...

@jonathanhefner great yak shaving in that ticket!

Unfortunately this is how `Module#autoload` works in this edge case. Let me explain with this snippet: ```ruby require 'tempfile' Tempfile.create(['foo', '.rb']) do |file| file.write(

This is a shell script that essentially does the same as the flaky test: ```bash #!/bin/sh cat