Pass on CursorNotFound errors from the mongodb to the client.
Added jruby-openssl for jruby platforms into the Gemfile to fix travis CI build failures.
Remove unnecessary code and update changelog
Better DNS resolution handling:

When DNS cannot resolve on Node initialization, the Node will now be
marked as "down" instead of raising a SocketError. Moped will attempt to
re-resolve the DNS on subsequent refreshes on the timer, and continue to
mark the node as down if it cannot be resolved.

[ close #71 ]
Update changelog
Bump version
Set SO_LINGER to false for socket connections
Handle Errno::EHOSTUNREACH in socket errors. [ fix #75 ]
Update changelog
Remove so_linger, bump version
Fixed a typo in the query failure handler of Node

This causes "ArgumentError: wrong number of arguments(0 for 1)" when a failover occurs

Sample backtrace (with Moped 1.2.2):
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:343 • has_key?
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:343 • block in query
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:532 • []
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:532 • block (3 levels) in flush
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:531 • map
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:531 • block (2 levels) in flush
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:123 • ensure_connected
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:527 • block in flush
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:542 • logging
config/initializers/moped_newrelic_instrumentation.rb:48 • block in logging_with_newrelic
vendor/bundle/ruby/1.9.1/gems/newrelic_rpm-3.4.2.1/lib/new_relic/agent/method_tracer.rb:242 • trace_execution_scoped
config/initializers/moped_newrelic_instrumentation.rb:45 • logging_with_newrelic
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:526 • flush
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:515 • process
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:341 • query
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/cursor.rb:116 • block in load_docs
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/session/context.rb:109 • block in with_node
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/cluster.rb:150 • block in with_primary
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/node.rb:168 • ensure_primary
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/cluster.rb:149 • with_primary
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/session/context.rb:108 • with_node
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/cursor.rb:115 • load_docs
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/cursor.rb:25 • each
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/query.rb:77 • each
vendor/bundle/ruby/1.9.1/gems/moped-1.2.2/lib/moped/query.rb:77 • each
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/contextual/mongo.rb:133 • block in each
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/contextual/mongo.rb:603 • selecting
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/contextual/mongo.rb:132 • each
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/contextual.rb:18 • each
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/criteria.rb:619 • entries
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/criteria.rb:619 • from_database
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/criteria.rb:310 • multiple_from_map_or_db
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/criteria.rb:176 • execute_or_raise
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/criteria.rb:243 • find
vendor/bundle/ruby/1.9.1/gems/mongoid-3.0.6/lib/mongoid/finders.rb:61 • find
app/controllers/application_controller.rb:37 • current_user
Update changelog, bump version
Update changelog
Don't include $orderby in updates.

This causes MongoDB to simply ignore the update command.

[ fix mongoid/mongoid#2430 ]
Bump version
Enable configurable retry periods on primary ops.

Moped::Session now can take 2 additional options, :retry_interval which
is the time to wait before attempting an operation on a primary again,
and :max_retries which is the maximum number of times to attempt the
operation before raising an error.

:retry_interval defaults to 1 (second).
:max_retries defaults to 30.

Instead of Moped attempting to perform an operation on the primary twice
before raising an error, it now refreshes the node list and retries
again up to the max number at retry intervals.

Related to: #80, #60

Thanks to Nicolas Viennot for the initial pull request to set the base
for the changes.
Enable configurable retry periods on secondary ops.

Instead of Moped attempting to perform an operation on a secondary
twice before raising an error, it now refreshes the node list and
retries again up to the max number at retry intervals.

Related to: #80, #60
Update changelog
legal checks on object ids support other object ids. [ fix #87 ]
Query hints are no longer erased on explain. [ fix #84 ]