awesome_print | Pretty print your Ruby objects | Application Framework library

First of all, the message about DidYouMean is a deprecation warning not an error, it doesn't break your app. It means that usage of DidYouMean::SPELL_CHECKERS is deprecated and will be removed in a future version of ruby. In this case in Ruby 3.3. You shouldn't worry about it until you use versions that are lower than 3.3. It's not your code that triggers the warning. It comes from a gem named Thor. The issue was solved in thor version 1.2.0. You can update the gem by calling bundle update thor.

The actual error comes from the bootsnap gem:

As mentioned in comments, per the README -- https://github.com/awesome-print/awesome_print, editing ~/.irbrc by adding these lines

Update:

It looks like it was a problem with my post-Bower configuration (I migrated from Bower --> Yarn) I was able to solve Sprockets errors by adding this line to my assets.rb:

Rails.application.config.assets.paths << Rails.root.join('node_modules')

and by running yarn add for files that Sprockets could not locate.

I also made the following updates to old package names in my `application.rb'

You can use pretty_inspect from stdlib pretty print(require 'pp') instead of regular inspect, that adds some formatting.

Classes from AuthorizeNet are huge and no formatting is the silver bullet. A more aggressive way is to monkeypatch inspect method for those to output only fields that are of interest to you

Webpacker changed from using .babelrc to babel.config.js between major versions 3 and 4. (Here is a link to the changelog where that is mentioned.) If this error pops up after the upgrade, it likely means that the legacy .babelrc file is still in the root of the Rails app. The solution is to delete .babelrc.

Zeitwerk (the autoloader used in Rails 6+) assumes that you declare constants in a file with the same name as the constant. scraper.rb is thus expected to declare the constant Scraper. Zeitwerk unlike the old autoloader will walk your autoloading directories at startup and index all the files which is why it complains even if you haven't referenced the constant Scraper.

You can configure Zeitwerk to ignore certain folders but you really should just get with the program and adjust your code to the autoloader. Start by renaming your file scraper_finder.rb and it does not belong in the controller directory since its not a controller. Place it in app/lib or app/clients or anywhere really is more suitable.

This is really only the tip of the iceberg through as this code is quite broken. What you actually want is something like:

This is almost certainly a permissions error.

Make sure that whatever file is readable: chmod a+r /opt/gitlab/embedded/service/gitlab-rails/config/database.yml (according to the comments you already did this) AND

Make sure that all the directories are executable, which for directories allows cd'ing into that directory:

Ok so this took a lot of debugging and going down a lot of different rabbit holes. The problem was very painfully simple. I created a class which I misspelled and called, GetLitsingsResponse. After changing the class back to GetListingsResponse Puma works just fine in my remote AWS Elastic beanstalk environment. It's very strange out locally on my Mac OS Puma had no problem. But in the 64bit Amazon Linux 2018.03 v2.11.4 running Ruby 2.6 (Puma) platform Puma would not function normally.