Skip to content

Can get e.g. “Your Ruby version is 2.1.1, but your Gemfile specified 2.1.2” when changing Ruby version without restarting Spring #314

Open
@henrik

Description

@henrik

I started a Rails 4 app with Ruby 2.1.1 but then I upgraded to 2.1.2 (in Gemfile and .ruby-version), and started getting this error e.g. opening a console or generating a migration.

It was fixed by running spring stop.

My theory is that Spring kept on running on 2.1.1 and so caused this error.

It was a bit painful. Is there any way a situation like this one could be detected and self-healed or give a better error message?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions