-
Notifications
You must be signed in to change notification settings - Fork 129
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
binding.b(do: ...) hangs Rails with puma web server #248
Comments
st0012
changed the title
binding.b(do: ...) hangs Rails server
binding.b(do: ...) hangs Rails with puma web server
Sep 4, 2021
This may be related: calling
But not
|
diff --git a/lib/debug/session.rb b/lib/debug/session.rb
index 977773e..25d5f29 100644
--- a/lib/debug/session.rb
+++ b/lib/debug/session.rb
@@ -304,6 +304,7 @@ module DEBUGGER__
if @preset_command.auto_continue
@preset_command = nil
@tc << :continue
+ restart_all_threads
return
else
@preset_command = nil
could you try it? the issue of simple thread example was solved with this patch. |
ah, I missed your PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Update: it doesn't happen when used with
thin
serverI just noticed that
binding.b(do: "")
hangs the Rails on puma server. But to be more clear, it doesn't hang the request that runs the command. It stops the next one from starting.An example:
As you can see, it finishes the request. But when I make a second request, it seems never reach the Rails server at all (no logs).
What's worse is that the process also doesn't accept any
Ctrl-c
(SIGINT
) exit.However, this is not the case for
binding.b
orbinding.b(pre: ...)
.So I suspect it has something to do with the present commands' auto continue mechanism.
The text was updated successfully, but these errors were encountered: