Comments on: Retrying code blocks in Ruby (on exceptions, whatever) http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/ Rails, Firefox, Anime, Mac Thu, 11 Mar 2010 23:55:41 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: A Ruby ‘tries’ method # Another code blog http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-731603 A Ruby ‘tries’ method # Another code blog Thu, 15 Oct 2009 03:10:32 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-731603 [...] exercise.   Tj Holowaychuk posted a retry method, which appears itself to be a refactoring of the retryable [...] [...] exercise.   Tj Holowaychuk posted a retry method, which appears itself to be a refactoring of the retryable [...]

]]> By: Loop Abstractions in D revisited http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-475634 Loop Abstractions in D revisited Thu, 31 Jan 2008 15:31:32 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-475634 [...] I showed you how we could make loop constructs abstract, in a similar way which is common in Ruby. The example I used as a model was the retryable method from Cheah Chu Yeow. His version is customizable in a way that let you [...] [...] I showed you how we could make loop constructs abstract, in a similar way which is common in Ruby. The example I used as a model was the retryable method from Cheah Chu Yeow. His version is customizable in a way that let you [...]

]]> By: www.hans-eric.com » Blog Archive » Loop Abstractions in D http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-450580 www.hans-eric.com » Blog Archive » Loop Abstractions in D Thu, 17 Jan 2008 21:32:38 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-450580 [...] with Ruby is the natural way in which you can hide looping constructs with descriptive names. Like the retryable example that Cheah Chu Yeow gives on his [...] [...] with Ruby is the natural way in which you can hide looping constructs with descriptive names. Like the retryable example that Cheah Chu Yeow gives on his [...]

]]> By: Chu Yeow http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-444102 Chu Yeow Tue, 15 Jan 2008 01:49:39 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-444102 You're right, Geoff and Jeremy! I wasn't aware the retry keyword worked for exceptions as well. I've updated the code :). You’re right, Geoff and Jeremy! I wasn’t aware the retry keyword worked for exceptions as well. I’ve updated the code :).

]]> By: Jeremy McAnally http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-443695 Jeremy McAnally Mon, 14 Jan 2008 18:10:32 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-443695 The retry keyword works for exceptions also. You could easily write a little helper to handle the retry counter, etc. The retry keyword works for exceptions also. You could easily write a little helper to handle the retry counter, etc.

]]> By: Geoff Buesing http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-443647 Geoff Buesing Mon, 14 Jan 2008 17:04:04 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-443647 I like this idea. I think you could avoid the double yield in your implementation by using Ruby's "retry" method: <code> rescue SomeError tries -= 1 retry if tries > 0 </code> I like this idea.

I think you could avoid the double yield in your implementation by using Ruby’s “retry” method:


rescue SomeError
tries -= 1
retry if tries > 0

]]> By: macournoyer http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-443558 macournoyer Mon, 14 Jan 2008 14:59:15 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-443558 very nice, I like your retryable method! very nice, I like your retryable method!

]]> By: Chu Yeow http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-443481 Chu Yeow Mon, 14 Jan 2008 12:35:57 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-443481 Yup exactly - I hated having to put conditionals in there for retries. Thankfully for Ruby blocks, we can abstract that considerably :) That sounds really nice, if we could monkey patch <code>rescue</code>, but I think it could be hard since <code>rescue</code>'s a language keyword. Yup exactly – I hated having to put conditionals in there for retries. Thankfully for Ruby blocks, we can abstract that considerably :)

That sounds really nice, if we could monkey patch rescue, but I think it could be hard since rescue’s a language keyword.

]]> By: rubylicio.us http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-443479 rubylicio.us Mon, 14 Jan 2008 12:32:10 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-443479 I ofcourse meant built into "rescue", not "retry" in the above post. I ofcourse meant built into “rescue”, not “retry” in the above post.

]]> By: rubylicio.us http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/comment-page-1/#comment-443478 rubylicio.us Mon, 14 Jan 2008 12:29:53 +0000 http://blog.codefront.net/2008/01/14/retrying-code-blocks-in-ruby-on-exceptions-whatever/#comment-443478 Good idea and nice little snippet, I usually tend to skip conditional retries, for no better reason then it feels like it clutters up my code alot ... which is a somewhat lame reason now that I think about it :) Wonder if this could be built into "retry" itself somehow .. <pre><code class="ruby">begin open('http://example.com/flaky_api') rescue OpenURI::HTTPError, :retries => 5 ## blah, errorreporting etc end</code></pre> Good idea and nice little snippet, I usually tend to skip conditional retries, for no better reason then it feels like it clutters up my code alot … which is a somewhat lame reason now that I think about it :)

Wonder if this could be built into “retry” itself somehow .. 

begin
  open('http://example.com/flaky_api')
rescue OpenURI::HTTPError, :retries => 5
  ## blah, errorreporting etc
end
]]>