wrangler 0.1.24 → 0.1.25

data/TODO

@@ -1,5 +1,9 @@
 This is a collection of things that could/should be worked on:
 
+== Interaction with other libs:
+* make compatible with newer versions of delayed_job...but maintain
+compatibility with the send_later() version.
+
 == Robustness:
 * in wrangler.rb : render_error_template(), if we fail to find a template for the
 exception/status code, we just log that fact right now. this is probably worth

data/lib/wrangler/exception_handler.rb

@@ -359,6 +359,39 @@ module Wrangler
     if render_errors
       render_error_template(exception, status_code)
     end
+
+  rescue Exception => unhandled_exception
+    # if it looks like a temporary error interacting with SMTP, then enqueue
+    # the error using delayed job if possible
+    # (testing by name this way in case the exception isn't loaded into
+    # environment, which would cause a NameError and be counterproductive...)
+    if unhandled_exception.class.name == 'Net::SMTPAuthenticationError' &&
+       Wrangler::ExceptionNotifier.respond_to?(:send_later)
+
+      log_error "Wrangler failed to send error notification: #{unhandled_exception.class.name}:"
+      log_error "  #{unhandled_exception.to_s}"
+
+      # note: this is specific to an old-ish version of delayed job...should
+      # make wrangler compatible with the old and the new...
+      log_error "Wrangler attempting to send via delayed job"
+        Wrangler::ExceptionNotifier.send_later(:deliver_exception_notification,
+                                              exception_classname,
+                                              error_string,
+                                              error_messages,
+                                              proc_name,
+                                              backtrace,
+                                              supplementary_info,
+                                              status_code,
+                                              request_data)
+    else
+      log_error "/!\\ FAILSAFE /!\\ Wrangler encountered an unhandled exception " +
+                "while trying to handle an error. The arguments it received " +
+                "were:"
+      log_error "  exception: #{exception.inspect}"
+      log_error "  options: #{options.inspect}"
+      log_error "The unhandled error encountered was #{unhandled_exception.class.name}:"
+      log_error "  #{unhandled_exception.to_s}"
+    end
   end
 
 

data/wrangler.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{wrangler}
-  s.version = "0.1.24"
+  s.version = "0.1.25"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Brian Percival"]
-  s.date = %q{2010-09-03}
+  s.date = %q{2010-09-21}
   s.description = %q{A gem for handling exceptions thrown inside your Rails app. If you include the
 gem in your application controller, wrangler will render the error pages you
 configure for each exception or HTTP error code. It will also handle notifying

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: wrangler
 version: !ruby/object:Gem::Version 
-  hash: 43
+  hash: 41
   prerelease: false
   segments: 
   - 0
   - 1
-  - 24
-  version: 0.1.24
+  - 25
+  version: 0.1.25
 platform: ruby
 authors: 
 - Brian Percival
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-09-03 00:00:00 -07:00
+date: 2010-09-21 00:00:00 -07:00
 default_executable: 
 dependencies: []