coderay | easy syntax highlighting for selected languages | Code Inspection library

I'm not really sure what happened and why but I tried doing this on my rails container and I was no longer receiving the said error.

1. docker-compose run --rm bash
2. cd to project directory
3. bundle install

Looks like you're running into compatibility issues trying to use the latest version of the activerecord-import gem at the time of writing (released in October 2020) with activerecord 3.2.22.5 (released in September 2016). You do mention it's a rails 3.2.15 app but you're not using activerecord 3.2.15 which is confusing.

Try using activerecord-import 0.4.1 (released in July 2013) and activerecord 3.2.15 which should be compatible with rails 3.2.15.

Rubygems overwrites Ruby's own Kernel#require method with its own method which loads gems on demand (i.e. adds the gem to the $LOAD_PATH and then requires the requested file).

Thus, when you execute require 'bundler/gem_tasks', what happens is that rubygems searches for a gem containing bundler/gem_tasks.rb in its require_paths path (which is specified in the respective gemspec of each gem). If a matching gem is found on your system, its require_paths are added to the $LOAD_PATH and Ruby's original require method is called which will load the requested file.

In any case, neither Ruby nor Rubygems dynamically loads gems from the internet. It will only use gems installed locally to the configured GEM_PATHS. You can find the configured paths which are searched for installed gems by running gem env on your command line.

If you start Ruby with the --disable-gems command line argument, it will not automatically load rubygems and thus will not add its custom implementation of Kernel#require. Here, only files in locations you specifically added to the $LOAD_PATH can be required.

Try updating your Gemfile to use json@1.8.2 instead of 1.8.1 - according to this thread Ruby 2.2.x is incompatible with json 1.8.1.

1.8.2 should be functionally similar and not affect any of your other dependencies.

You can also run bundle update json to let bundler try to fix it for you - but that may put you at a much later version than 1.8.2, I'm not sure.

No harm in trying a couple things and reverting your changes.

I think I see what's going on. In your Dockerfile, change your DB_URL from: mysql:// to mysql2://

You are loading the mysql2 gem, but indicating to ActiveRecord that you want to use a connection via the mysql gem.

When you require 'sinatra' certain magic things happen that brings a bunch of stuff into scope and essentially turns your app.rb into an instance of Sinatra::Application. The cookies method is only defined on instances like this – it isn’t present on other classes automatically.

What you probably want to do is turn your helper into a real Sinatra style helper by making it a module and then loading it using the helpers keyword, which will just make these instance methods:

This is probably and error with the stylesheet_link_tag and stylesheet_pack_tag, check out your layout files probably you are including sass files and you are using stylesheet_link_tag, this is breaking your code given that as I understand you can just link plane css files. so if you are including sass files use the stylesheet_pack_tag

Jekyll default config : baseurl: "" # the subpath of your site, e.g. /blog

Your baseurl must be empty.

The original implementation of Kernel#require returns true or false. Your new require method does not return that value anymore instead it always returns nil (the response from the p method).

I can imagine that in some cases it makes sense to have a condition in your code and define constants depending on the response of the require.

You can probably fix the issue by swapping the lines in your method: