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
Bootsnap::LoadPathCache::FallbackScan #250
Comments
1.2.0 is pretty old. Is that the version this is happening on? Can you try upgrading to the latest release? Or, which version are you actually running? |
I am running bootsnap (1.4.1) as mentioned in Gemfile.lock above. I upgraded from 1.2.0 to 1.4.1 |
@burke found the issue. Bootsnap is overriding other load errors. Without bootsnap i am getting following error. |
I'm still seeing this |
I'm running Bootsnap 1.4.5, rails 6.0.2.rc1. Everything works great under ruby2.7.0 preview1, but errors with Bootsnap::LoadPathCache::FallbackScan under ruby2.7.0 preview2. |
I just updated my Ubuntu install from 19.10 to 20.04 LTS and got this error on |
Having this raised randomly inside RSpec tests with OS X Catalina / Ruby 2.7.1 / Rails 6.0.3.1 / Bootsnap 1.4.5 |
i am still getting Caused by: when i run rails webpacker:install with gem react-rails |
I ran into similar issue today. The actual cause was printed as the last error message at the bottom:
|
Anyone who gets this error along with
This probably makes sense to add to your .bashrc or another file that is sourced every time you run your terminal. |
This was fixed in #314 |
I have upgraded my app from 5.1.0 to 5.2.2 and we were already using the bootsnap version 1.2.0 in rails 5.1.0
After upgrade i am getting following error at different pages.
Bootsnap::LoadPathCache::FallbackScan
I have deleted the
tmp/cache
already, but it didn't work. Also i tried to downgrade the gem but it require active-record < 5.2 and for rails 5.2.2, it require active-record 5.2.2I also tried to use latest code from github, but the issue persist.
Following are the details of my code.
Error StackTrace
Boot.rb
Gemfile.lock
The text was updated successfully, but these errors were encountered: