font-awesome-rails | awesome font bundled as an asset for the rails asset | User Interface library

I am using Rails 6.1.3 with Ruby 2.7.2 for a mostly static pages app. The app has a registration form that a student must complete and download as a PDF file to print, persistence is not required at this point. It was working fine with Dhalang (Google's puppeteer wrap) gem, then I did a Javascript routine for a different part of the app and it stopped to work. The process should be: A view has a button link_to the route "new_student_url" set up to the "students_controller#new" action which should get the views/students/new to render the _form, At this point I have the button pointing and recognizing the route but when I click on it it just ignores the event; Oddly enough, if I right click the button to 'open link in a new tab', it works... =/ I have read several other cases and found that most of them are caused by a Turbolinks issue, so I did review my Turbolinks setup with Webpack and the app/javascript/packs/application.js seems to be ok, please help.

This is the link button:

I have cloned an existing project and trying to run it in my system. Since this is the first time I don't have any Gemfile.lock file in my directory. I tried running bundle install and the following errors occur:

I'm helping a friend with a project, but after helping him with the logic instead of merging my branch, for some reason he copied the code and added it himself. So my branch remained "behind". He kept working and now he asked me to help him with something else, but I had a bunch of conflicts to resolve before working on the new logic, I tried to resolve the conflicts manually but something must have slipped my check, because now I have a bunch of conflicts in the Gemfile.lock that I don't know how to fix. Can you guys give it a check? Thank you so much!

I updated my ruby to 3.0.0 but for some reason now my application doesn't work. I have searched online for different answered but I cannot find anything. This error has gotten me going crazy now. Here is what happens.

When I do bundle update I get:

I'm trying to revive an old Rails application I worked on several years ago. I'm using ruby 2.3.3 and rails 3.2.15 on the Heroku-16 stack with ClearDB for my MySQL database with the mysql2 adapter. When deploying to Heroku it succeeds on the deploy but crashes when it tries to start the app.

Full stack trace from the Heroku log (updated after fixing activerecord-import gem version per suggestion in first answer):

I am getting an error trying to run Spree 3.3 after following the steps to upgrade from 3.2 at https://guides.spreecommerce.org/developer/upgrades/three-dot-two-to-three-dot-three.html. I updated the Gemfile, ran bundle update, and then installed the migrations. I couldn't even run the migrations because of this same error:

I picked up a 4 year old project written in Ruby 2.1.3 and Rails 4.1.8.

Very few of the gems were versioned but I've managed to get the project running locally by installing mysql2 0.3.20 as suggested in multiple other threads. Doing this required me to (on MacOS) downgrade openssl and mysql with brew install mysql@57 and brew install openssl@10.

I could then install mysql2 with by passing the correct libraries to it: gem install mysql2 -v 0.3.20 -- --with-mysql-config=/usr/local/opt/mysql@5.7/bin/mysql_config --with-ldflags=-L/usr/local/opt/openssl@1.0/lib --with-cppflags=-I/usr/local/opt/openssl@1.0/include

Everything works locally, all good.

I'm trying to deploy this project with Dokku on a Debian instance. Here's the readout from the push to dokku master including the error thrown when starting the Rails server:

maybe is a dumb question, but I am having an issue when I am trying to run a test on Ruby, this is the error:

Error: UsersLoginTest#test_login_with_valid_information:

NoMethodError: undefined method User' for # Did you mean? super test/integration/users_login_test.rb:6:insetup'

I tried to fix the fixture .yml but I am not sure that the problem is there anymore.

This is my users.yml

I have a problem when I am deploying in Heroku: