Jere Robles comments

Results 5 comments of


                                            Jere Robles

Connection refused error after updating to 1.6.X in a Rails project running inside docker

Could `@need_pause_at_first` have something to do with this?

Connection refused error after updating to 1.6.X in a Rails project running inside docker

Or perhaps https://github.com/ruby/debug/blob/master/lib/debug/server_dap.rb#L135

Connection refused error after updating to 1.6.X in a Rails project running inside docker

@ralph @ko1 it actually works without the `-n` flag but then it's unusable. Also the following issues share the same root cause as this one * https://github.com/ruby/debug/issues/368 * https://github.com/connorshea/vscode-ruby-test-adapter/issues/92#issuecomment-1191477785 I...

Connection refused error after updating to 1.6.X in a Rails project running inside docker

Thanks for this @ralph! I can also confirm using binstub works on 1.6.x However, I still see the EADDRINUSE flood from 1.5.x: ``` /usr/local/lib/ruby/2.7.0/socket.rb:201:in `bind': Address already in use -...

Connection refused error after updating to 1.6.X in a Rails project running inside docker

@ralph okay! Looks like the socket is a bit more reliable than TCP. Have you tried remote debugging (maybe with VSCode) using UDS?