You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Console evaluation in Chrome devtools debugging session #894
When debugging via open chrome, I can step through code and set breakpoints fine, but when I enter even 1 character into Chrome's console to test evaluating something, the debugger crashes and its attached ruby process with it.
(eval):1:in `block in process_protocol_request': No such file or directory @ rb_sysopen - -b (Errno::ENOENT)
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/server_cdp.rb:759:in `eval'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/server_cdp.rb:759:in `block in process_protocol_request'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/server_cdp.rb:758:in `map'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/server_cdp.rb:758:in `process_protocol_request'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/session.rb:424:in `wait_command'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/session.rb:377:in `block in wait_command_loop'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/session.rb:376:in `loop'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/session.rb:376:in `wait_command_loop'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/session.rb:342:in `process_event'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/session.rb:235:in `session_server_main'
from /usr/local/bundle/gems/debug-1.7.1/lib/debug/session.rb:197:in `block in activate'
🤔 I found that I'm having this issue in one environment but not another. I'll see whether I can find time to trace down what's wrong in the environment where it's broken.
Activity
nilbus commentedon Feb 10, 2023
🤔 I found that I'm having this issue in one environment but not another. I'll see whether I can find time to trace down what's wrong in the environment where it's broken.
ono-max commentedon Mar 11, 2023
I think that #893 fixes this issue.
If you have any problem, please reopen or mention me. Thank you.