debug
debug copied to clipboard
ruby
Change the log level for the fork interception
Your proposal
Stop logging it as WARN, start logging it as TRACE or DEBUG.
Additional context
It obscures normal execution.
If you're talking about these messages: "Detaching after fork ...." and "Attaching after process ...", I think they can be downgraded to debug in the future. But at the moment, the forking mechanism isn't completely stable and can cause issues like #336. Having this message can help users be aware of process forking and identify/report the problem.
When I run RSpec against Rails 7 application, I see this warning. It's noisy a little to read the result of tests.
$ bundle exec rspec -f progress
...................................................................DEBUGGER: Attaching after process 69034 fork to child process 69055
...
Finished in 3.26 seconds (files took 1.79 seconds to load)
70 examples, 0 failures
In addition, this warning is displayed in red when I run tests within RubyMine's terminal. I sometimes misunderstand that something is wrong with my application.
I'd be glad if it is suppressed by default.
