When Zeus doesn’t work…

Do you work with Rails? and is it not a brand spanking new Rails 4, but the older and less-loved, relatively speaking, version?

Then, you must have come across Zeus. It’s pretty handy if you like to test drive your code from outside-in and aren’t scared to venture into the dark and a tad dragging land of integration specs. A normal Zeus workflow is, to start the server first, and then issue commands to the server from the client. Simple!

However, it’s not always like it. You may come across unhelpful error messages, like the following when you start the server:

1.

exit status 1 and then run tests.

2.

Could not find 'zeus' (>= 0) among 214 total gem(s) (Gem::LoadError)

Both the error messages are quite random. Googling the first one will reveal a lot of reasons and ways to fix it, second one is just a normal gem error message when the gem is not found. In both the cases, I found the reason for the error to be some gems missing from project’s bundle and installing those gems fixes the issue.

So, next time when you pull upstream changes, and Zeus stops working, try running bundler’s install command.

Hope it helps.

About andhapp

Namastey (Hello) Stranger, This is not the geekiest blog on the planet yet it is not the dumbest one either. I am a small time developer who likes to explore new technologies. I usually program in Java, Groovy and Ruby and take keen interest in the surrounding geeky developments.
This entry was posted in Uncategorized and tagged , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>