wasifhossain
commented
4 years ago usually logs contain long traces of files that were touched along the way while executing some code in your project, but ending up with some errors.
most of the times, its highly likely there's some code in your project which resulted in that error. In such case, you just need to trim down the log in your mind by only looking at the traces that point to some code in your project only.
let's assume that we got the following lines from the above log that are inside your project, including any error messages:
Traceback (most recent call last):
bin/rails: Bootsnap::LoadPathCache::FallbackScan
50: from bin/rails:3:in `<main>'
49: from bin/rails:3:in `load'
48: from /home/abir/environment/sample_app/bin/spring:15:in `<top (required)>'
...
38: from /home/abir/environment/sample_app/bin/rails:9:in `<top (required)>'
...
12: from /home/abir/environment/sample_app/config/application.rb:7:in `<main>'
...
/home/abir/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require': cannot load such file -- rspec-api_helpers (LoadError)
...
/home/abir/.rvm/gems/ruby-2.6.5/gems/bootsnap-1.4.5/lib/bootsnap/load_path_cache/core_ext/active_support.rb:60:in `block in load_missing_constant': uninitialized constant RSpec::Matchers (NameError)Note that, I skipped the duplicate lines relevant to your project.
here we can see that the last line is highlighting the real error message, whereas everything else are just traces how rails came to the error.
Lets assume we have got this log containing some errors
How can we extract the actual error messages that we need in order to resolve the error?