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

Cannot read echo when using byebug or debugger tool #703

thedon-chris opened this Issue Feb 27, 2018 · 3 comments


None yet
4 participants
Copy link

thedon-chris commented Feb 27, 2018


I am using foreman alongside a debugger tool inside of Ruby on Rails applications. Foreman is managing my puma server, redis-server, workers, and mailcatcher.

When I use a debugger tool alongside foreman, I cannot read the echo of my commands. This becomes really frustrating during the debugging process.

Can anyone please help?


This comment has been minimized.

Copy link

fakhir-shad commented Jun 1, 2018

I am also experiencing this issue. In the debugger, I am not able to see what I am typing.


This comment has been minimized.

Copy link

ColinTheRobot commented Jun 6, 2018

Yep, there's a closed issue #58 here with some old stuff about using pry-remote. But haven't been able to get it to work yet


This comment has been minimized.

Copy link

skyksandr commented Nov 20, 2018

I've faced a similar problem and looks like I've found a good workaround -
So all you need is to write a script that feeds arguments to it.

Here is my example:
concurrently -p '[{name}]' --handle-input -n back,front -c 'black.bgGreen,black.bgCyan' 'rails s' 'bin/webpack-dev-server'

Here is how it looks like:
2018-11-20 17 21 06

PS most important flag here is --handle-input. Debugging just works

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment