-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trying to debug minitest #16
Comments
Does minitest work if you specify an explicit file and line, e.g., instead of |
That doesn't work, no. I've also tried without the line-number in the path, just to be sure, but same results. |
This might be related to how the debugger's process monitor manages threads. I haven't identified a root cause yet, but I'm looking into it. |
If there's anything I can do, please let me know |
I have the same problem. I see two threads appear in the call stack, then disappear immediately. I don't see any output in the debug console though. Any progress on this? |
Trying to debug a minitest, using the following configuration.
But basically nothing happens, I see rails starting in the debug console, but the process ends straight away without debugging. Am I doing something wrong? I see threads starting in the call stack. I have "break on raised exceptions" off, because otherwise I'd see all exceptions (caught or not).
Clicking on "Debug" here doesn't work, as that is tied to the ruby plugin.
I've tried useBundler: true, but that gives the same results.
Debugging using 'rails server', using the following configuration works:
It quickly ends in: "fatal (exception reentered):" though - in:
/Users/tdegrunt/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/actionpack-6.1.4/lib/action_dispatch/middleware/static.rb:140
The text was updated successfully, but these errors were encountered: