You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RubyMine 2020.1.1
Build #RM-201.7223.94, built on April 30, 2020
Runtime version: 11.0.6+8-b765.40 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.15.6
GC: ParNew, ConcurrentMarkSweep
Memory: 1979M
Cores: 12
I launch the app in debug mode, here's the command and ports RubyMine injects at debug launch:
app_1 | Fast Debugger (ruby-debug-ide 0.7.2, debase 0.2.4.1, file filtering is supported) listens on 0.0.0.0:1234
app_1 | => Booting Puma
app_1 | => Rails 5.1.3 application starting in development on http://0.0.0.0:3000
app_1 | Puma starting in single mode...
app_1 | * Version 3.10.0 (ruby 2.4.1-p111), codename: Russell's Teapot
app_1 | * Min threads: 1, max threads: 1
app_1 | * Environment: development
app_1 | * Listening on tcp://0.0.0.0:3000
I set the breakpoint in RubyMine before loading the app on browser. Loading after results in an IOError. The app is unresponsive thereafter and would require a restart and launched without adding breakpoint for it to load in debug mode.
Having a world of trouble getting breakpoint to stick in the app when running the app in debug.
I went through the process in setting up RubyMine with docker-compose for the project here following these steps:
https://blog.jetbrains.com/ruby/2019/03/rubymine-docker/
RubyMine specifics in my environment
I launch the app in debug mode, here's the command and ports RubyMine injects at debug launch:
Here's what's in the logs
I set the breakpoint in RubyMine before loading the app on browser. Loading after results in an IOError. The app is unresponsive thereafter and would require a restart and launched without adding breakpoint for it to load in debug mode.
Here's the full stack trace:
If I launch the app in debug mode without breakpoint and then add breakpoint, it's just ignored.
Any pointers would be immensely appreciated. Thanks.
The text was updated successfully, but these errors were encountered: