Debugging rspec with spring

 Rails 5 preloads way more than Rails 4 did. That slows initial spin up time way down. Since updating a large application to rails 5, my debugger is totally worthless. It takes a solid 3 minutes or so to connect and start up. This is true for a rails server (debug mode), or rake task, or rspec, etc. Anything in debug mode is now a joke to start.

I notice the "use preload server" options, and have selected spring, but i get a little message popup saying it wont use it while debugging. This defeats the purpose completely right?

How can I fix? I've had to start using pry which I hate for debugging.

8 comments
Comment actions Permalink

Hello, sorry for delay, we need more  logs to figure out the problem. Please switch on in 'Settings | Debugger | Verbose debugger output' and run debug again, then attach all output with all content of log files. See where:https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs. By the way, is it possible to get sample of your project?

0
Comment actions Permalink

Thanks for the reply. I cannot share the exact repository with you, but here is the open source version which is very close: https://github.com/instructure/canvas-lms I have not tried debugging on the open source version, so i'm not 100% sure if the same problem exists there. I will say though, that this application is large enough to where rubymine has TONS of issues. it takes forever to load, every time I open a model, or any large file, it struggles bad, and freezes up big time. I have to turn all inspections off to even have a fighting chance. I also have to ignore all of the JS files.

Back to the problem at hand though, I've enabled verbose debugging and cleared out all previous log files. I closed, and re-opened rubymine, then ran one of the specs in debug mode. It generated some output in idea.log file. Is there a place I can send these logs to you directly? I would rather not have them public.

Thanks!

 

0
Comment actions Permalink

Thanks for example, need time to reproduce. Please send me logs to anna.kutarba@jetbrains.com

0
Comment actions Permalink

Is there any update on this? I don't believe the issue you associated this with (https://youtrack.jetbrains.com/issue/RUBY-18263) is the same issue I described above.

Thanks

0
Comment actions Permalink

What is being done about this? I've upgraded to 2017.3 (Build #RM-173.3727.132, built on November 28, 2017) just now, and updated the debugger gem. I just timed it and it took a full 4:09 from the time I clicked run with debug on a single spec till the time it actually started.

0
Comment actions Permalink

The original YouTrack issue is reopened so please follow it.

0
Comment actions Permalink

Are you talking about this ticket?

https://youtrack.jetbrains.com/issue/RUBY-18263

 

I just watched the video for this reported bug, and it doesn't appear to have anything to do with my issue. Can we open a new ticket for this one? I can get a video recorded as well as some logs, but really you should have zero problem replicating this by pulling the repo I referenced above, and trying to run specs in debug mode.

0

Please sign in to leave a comment.