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

Pry doesn't work well with bootsnap #2159

Closed
aniketstiwari opened this issue Nov 4, 2020 · 1 comment
Closed

Pry doesn't work well with bootsnap #2159

aniketstiwari opened this issue Nov 4, 2020 · 1 comment

Comments

@aniketstiwari
Copy link

Whenever i place debugger for the first time it works fine. But for the second time the debugger goes into ruby internal. I check this seems to be an existing issue with byebug deivid-rodriguez/byebug#452

I tried few things by adding disable_trace: false still the issue is reproducible Shopify/bootsnap#281

My bootsnap configuration

Bootsnap.setup(
cache_dir: 'tmp/cache', # Path to your cache
development_mode: 'development', # Current working environment, e.g. RACK_ENV, RAILS_ENV, etc
load_path_cache: true, # Optimize the LOAD_PATH with a cache
autoload_paths_cache: true, # Optimize ActiveSupport autoloads with cache
compile_cache_iseq: true, # Compile Ruby code into ISeq cache, breaks coverage reporting.
compile_cache_yaml: true, # Compile YAML into a cache
disable_trace: false
)

Rails - 5.2.4.4
ruby - 2.5.3
Bootsnap - 1.4.1
pry - 0.12.2
pry-rails 0.3.9

@barrettkingram
Copy link
Contributor

I was able to reproduce this with ruby 2.5.7. The problem was resolved for me by changing the compile_cache_iseq option to false. This is the default in bootsnap 1.4.4 and higher. Shopify/bootsnap#257 has some more context on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants