slim-rails | Slim templates generator for Rails

The problem is that you have slim-rails in the development group in your Gemfile and you're running the test environment. I can't possibly think of a scenario where you would actually want different template engines per environment.

Just move it out of the development group.

Most likely you have some strong constraints on some particular gems in your Gemfile that's it's blocking bundle from updating a dependency.

The solution was to lock the version of capistrano3-puma to 4.0.0:

How I solved it:

1. Go to server command line
2. As we can see in error log, the last command before error appears was:

Command: cd /home/deploy/project/releases/20201018151933 && ( export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check )

So we go to our folder:

cd /home/deploy/project/releases/20201018151933

and run there command:

export RAILS_ENV="production" RBENV_ROOT="$HOME/.rbenv" RBENV_VERSION="2.6.5" ; RBENV_ROOT=$HOME/.rbenv RBENV_VERSION=2.6.5 $HOME/.rbenv/shims/bundle exec bundle check

After that we see same error:

Could not find concurrent-ruby-1.1.7 in any of the sources. Run 'bundle install' to install missing gems.

1. In same folder run bundle install and after gem installed we can out of server command line.
2. Run cap production deploy and everything is gonna be fine.

I still don't know what is the root problem of this error, and how to fix it permanently, but this works for me. I hope it will be useful for anyone else.

Try this:

.click *{ data: { logined: "#{sth}", review: "#{love_type ? target : nil }", recommend:"#{love_type ? nil : target}" } }

Or you can use a helper method to return data as a hash:

.click *{ data: as_a_hash(love_type) }

helper_method:

Thanks to @Les Nightingill, I found the issue.

It was not directly linked to assets generation, but the probleme was indicated at the first error line in the logs :

The url_for is the view context path to the image.

To access the image internally, you need to use rails_blob_path

From the documentation...

If you need to create a link from outside of controller/view context (Background jobs, Cronjobs, etc.), you can access the rails_blob_path like this:

Rails.application.routes.url_helpers.rails_blob_path(user.avatar, only_path: true)

https://edgeguides.rubyonrails.org/active_storage_overview.html

The root of the problem seems to be bundler. What operating system and Ruby version are you using? It may be a problem with old OpenSSL library, so you can not install bundler and everything after it.

If you are using jRuby (your gem list output tells so), your problem seems to be the same as described in link. And there is a solution as well.

Maybe you forgot to set 2.1.2 version of ruby as global? (rbenv set global 2.1.2)

It turned out that my active_job.queue_adapter has been overridden by my config/environment/development.rb as pointed out above by @max pleaner. I just removed the active_job.queue_adapter = :inline and it fixed my problem! :)