In the GOV.UK email system, we've had to add our own error handling around calls to .send_email for unactionable / transient network errors, so we don't get notified about them (vs. other, fixable errors):

• Net::OpenTimeout
• Net::ReadTimeout
• SocketError (getaddrinfo: Name or service not known)

Would it be possible to wrap these exceptions and expose one or two custom exceptions we could handle instead? This means we can decouple our code from the low-level request implementation.

(Note that we don't want to ignore these errors generally on GOV.UK, since they might indicate a real issue e.g. if we don't have a robust retry mechanism. In this case, we retry sending email many times.)

Hi,

I get a load error when attempting to use the notifications-ruby-client gem:

$ irb
>> require 'notifications-ruby-client'
LoadError: cannot load such file -- notifications-ruby-client
    from /usr/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /usr/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from (irb):1
    from /usr/bin/irb:11:in `<main>'

Operating systems: CentOS 7, macOS Sierra 10.12
Ruby versions: ruby 2.4.0preview1 (2016-06-20 trunk 55466) [x86_64-linux], ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin16]

The instruction say:
client = Notifications::Client.new(api_key)

But this returns:
ArgumentError: wrong number of arguments (given 1, expected 2..3)

The Speaker class expects a service_id and an api_secret. Can you clarify that the api_secret is the same as the API key that can be configured through the Notify admin console?