Dynamoid does not fail correctly if it cannot connect to an endpoint about dynamoid HOT 4 CLOSED

Yes, new maintainers just came on board. We are working through the issues now. Also, please try the new release 1.2.1.

from dynamoid.

I am also experiencing this error but in a slightly more bizarre circumstance. When I have my Rails app and DynamoDB local running in a docker-compose cluster, everything works great. I'm able to save and query for objects in DynamoDB just fine. When I run the Rails app in Docker but run DynamoDB in a separate VM or locally on my laptop, even though I am able to telnet to the right port on the host machine from Docker, I get this error. I also get it if DynamoDB local isn't running.

The swallowing of exceptions most definitely needs to get fixed on the concurrent-ruby side of things, but I suspect something else might be going on here. It takes nearly 5 minutes to time out, too, so this has been really hard to figure out.

This issue has been open for over a month now. Is anyone actively developing Dynamoid still?

from dynamoid.

Currently I reproduce meaningful Seahorse::Client::NetworkingError exception (dynamoid-2.0.0).

.../ruby/2.4.0/net/http.rb:906:in `rescue in block in connect': Failed to open TCP connection to localhost:3000 (Connection refused - connect(2) for "localhost" port 3000) (Seahorse::Client::NetworkingError)

@pboling Maybe we need to wrap it with Dynamoid's exception like Dynamoid::Errors::NetworkError

Script to reproduce

require 'aws-sdk'
require 'dynamoid'

Aws.config.update({
  region: 'us-west-2',
  credentials: Aws::Credentials.new('REPLACE_WITH_ACCESS_KEY_ID', 'REPLACE_WITH_SECRET_ACCESS_KEY'),
})

Dynamoid.configure do |config|
  config.endpoint = 'http://localhost:3000'
end

class Document
  include Dynamoid::Document
end

Document.create_table

from dynamoid.

I think we should allow the underlying transport errors to bubble up. 👍

from dynamoid.