-
Notifications
You must be signed in to change notification settings - Fork 127
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
key typing as ASCII sequences, and then freezes Ruby #871
Comments
Sorry, I couldn't repr. On the stack overflow, DatabaseCleaner is related, but I have no knowledge about it. |
From the symptoms, it may have the same cause as #877. This is because by default typing up arrow key uses One way to verify it is to add |
I'm seeing the same behavior with going back in history using the up arrow on macOS, and |
I've managed to reproduce it pretty consistently, and get this error:
I couldn't get a minimal repro case, I think it probably depends on the usage of faraday in my gem to eat up some of the threads? Not sure. Here are the best repro steps I can get, I tested it on Ruby 3.2.0 but it may happen on 3.1 as well:
I hope that helps! |
I am also seeing the same error. AFAIS, after I press any arrow keys for the second time, the process fails with the below error.
Output of bundle env;
I am getting this error when I run the below code via
FWIW, |
Or using remote REPL ( |
RUBY_DEBUG_NO_RELINE=1 doesn't help. I have to terminate Ruby via System Monitor every 5 minutes of debugging. |
RUBY_DEBUG_NO_RELINE doesn't help, test just fails on binding.break with ENOENT.
|
Appears fixed in recent versions. |
Your environment
ruby -v
: 3.1.2rdbg -v
: 1.7.0Describe the bug
From stack overflow:
"Ruby
debug
gem does not accept arrow keys and shows the key typing as ASCII sequences, and then frozes"+1
binding.break
This is the result of up arrow key presses:
^[[A^[[A^[[A^[[A^
The text was updated successfully, but these errors were encountered: