Since Radiator had a big update involving node reliability, here are some tips to update any apps that rely upon it. There are a few options.
If it ain't broke, don't fix it ...
If you're not having any problems, maybe you don't need to update. Or, just make a backup to fiddle with.
Ignore warnings ...
If you're only seeing warnings from time-to-time, it's probably nothing to worry about. Nodes go up and down, so it's not a big deal.
Just update the gems ...
Sometimes, all you need to do is update the gems (ruby libraries). Here's the command for that:
$ bundle update
Update the app ...
This is the most tricky option. If you have modified any of the files in the project, your changes must be merged with the update. Often, git can handle this automatically. But often it can't, so it's best to make a backup first in case you need to re-clone the project.
$ git stash
$ git pull
$ git stash pop
$ bundle install
$ bundle update
In a nutshell, we're telling git to save a copy of the modifications (git stash), getting the latest project files (git pull), then merging any changes (git stash pop). If that works without any errors, new gems can be installed (bundle install).
We also do a bundle update because not all apps know about the latest gems after installation.
You can try to repair it with these comments:
$ git checkout -- Gemfile.lock
$ git reset *.yml
This will completely clobber the changes in Gemfile.lock so it can be recreated. We are also telling git not to worry about previous merges to the configuration files. Now you can retry the update.
If you still have problems, you can always follow the initial installation steps for the particular app, see: My App Catalog