Skip to content
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

Add a workaround to make IRB work with debug's tests #919

Merged
merged 1 commit into from
Apr 10, 2024

Conversation

st0012
Copy link
Member

@st0012 st0012 commented Apr 10, 2024

No description provided.

@k0kubun
Copy link
Member

k0kubun commented Apr 10, 2024

Merging to fix ruby/ruby CI.

@k0kubun k0kubun merged commit eb442c4 into master Apr 10, 2024
57 checks passed
@k0kubun k0kubun deleted the workaround-debugger-failure branch April 10, 2024 23:16
st0012 added a commit to Shopify/debug that referenced this pull request Apr 11, 2024
…ests

When investigating the issue related to ruby/irb#919,
I realized that console tests aren't executed with the IRB version specified
in the project's Gemfile. This is because the rdbg command passed to PTY process
doesn't use Bundler.

This commit changes the PTY's rdbg command to use Bundler if the test is
executed with it. This will make it significantly easier to
debug issues related to IRB or Reline changes.
st0012 added a commit to Shopify/debug that referenced this pull request Apr 11, 2024
When debugging the issue related to ruby/irb#919,
I noticed that debugger tests don't respect the IRB version I specified
in the Gemfile. This is because console tests force override the RUBYOPT
env, which will remove the `-rbundler/setup` injected by bundler.

Further more, if tests use `run_rdbg` with the `rubyopt` option, the
RUBYOPT will be overridden yet again.

So in this commit I did 2 improvements:

1. `run_rdbg` should append instead of override RUBYOPT
2. If tests are executed with bundler, we also run the debugger in PTY
   process with bundler by appending `-rbundler/setup` to RUBYOPT
st0012 added a commit to Shopify/debug that referenced this pull request Apr 11, 2024
When debugging the issue related to ruby/irb#919,
I noticed that debugger tests don't respect the IRB version I specified
in the Gemfile. This is because console tests force override the RUBYOPT
env, which will remove the `-rbundler/setup` injected by bundler.

Further more, if tests use `run_rdbg` with the `rubyopt` option, the
RUBYOPT will be overridden yet again.

So in this commit I did 2 improvements:

1. `run_rdbg` should append instead of override RUBYOPT
2. If tests are executed with bundler, we also run the debugger in PTY
   process with bundler by appending `-rbundler/setup` to RUBYOPT
st0012 added a commit to Shopify/debug that referenced this pull request Apr 11, 2024
When debugging the issue related to ruby/irb#919,
I noticed that debugger tests don't respect the IRB version I specified
in the Gemfile. This is because console tests force override the RUBYOPT
env, which will remove the `-rbundler/setup` injected by bundler.

Further more, if tests use `run_rdbg` with the `rubyopt` option, the
RUBYOPT will be overridden yet again.

So in this commit I did 2 improvements:

1. `run_rdbg` should append instead of override RUBYOPT
2. If tests are executed with bundler, we also run the debugger in PTY
   process with bundler by appending `-rbundler/setup` to RUBYOPT
st0012 added a commit to Shopify/debug that referenced this pull request Apr 18, 2024
When debugging the issue related to ruby/irb#919,
I noticed that debugger tests don't respect the IRB version I specified
in the Gemfile. This is because console tests force override the RUBYOPT
env, which will remove the `-rbundler/setup` injected by bundler.

Further more, if tests use `run_rdbg` with the `rubyopt` option, the
RUBYOPT will be overridden yet again.

So in this commit I did 2 improvements:

1. `run_rdbg` should append instead of override RUBYOPT
2. If tests are executed with bundler, we also run the debugger in PTY
   process with bundler by appending `-rbundler/setup` to RUBYOPT
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants