Closed printinghappy closed 10 years ago
ranmocy
commented
10 years ago No. You didn't miss anything. Currently, it can't be used because Guard-rails runs rails in another thread in background. And I can't join the thread because that will block the whole guard process. I didn't find any way to make it possible to use any debugger gem in guard-rails now. If you find any guard's plugin can use debugger or pause for input, please please let me know. Thank you.
printinghappy
commented
10 years ago Thanks for letting me know. Would be great to have it in the future.
Sent from my iPad
On Jul 4, 2014, at 11:27 PM, Ranmocy Sheng notifications@github.com wrote:
No. You didn't miss anything. Currently, it can't be used because Guard-rails runs rails in another thread in background. And I can't join the thread because that will block the whole guard process. I didn't find any way to make it possible to use any debugger gem in guard-rails now. If you find any guard's plugin can use debugger or pause for input, please please let me know. Thank you.
— Reply to this email directly or view it on GitHub.
I'm probably missing something, but I can't seem to get debugger to work while using guard and guard-rails. Debugger works fine when running outside of guard like so:
bundle exec rails s
...but using guard, the "debugger" line is skipped over:
bundle exec guard => ... (rdb:1) Event Load (1.4ms) SELECT DISTINCT(occurred_at) FROM "events" ORDER BY occurred_at ASC LIMIT 1 Event Load (0.8ms) SELECT DISTINCT(occurred_at) FROM "events" ORDER BY occurred_at DESC LIMIT 1 ...
I'm running a Rails 4.1.1 app and guard-rails 0.5.2 (latest at the time of this writing). I've tried passing "debugger: true" as an option and I do see "Debugger enabled" as a result. I've also tried switching from thin to webrick. Any thoughts would be appreciated!