0

我有一个 ruby​​ on rails 应用程序，它rake tweet每小时执行一次，从数据库中发送一条推文。在查看了我发现的日志后，我注意到有几次推文没有发送：

2013-02-11T19:00:39+00:00 app[scheduler.8796]: Connecting to database specified by  DATABASE_URL
2013-02-11T19:00:39+00:00 app[scheduler.8796]: (__-){ Twitter is over capacity.
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/twitter-4.5.0/lib/twitter/response/raise_error.rb:21:in `on_complete'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.5/lib/faraday/response.rb:9:in `block in call'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: rake aborted!
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.5/lib/faraday/response.rb:8:in `call'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.5/lib/faraday/response.rb:8:in `call'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.5/lib/faraday/response.rb:63:in `on_complete'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.5/lib/faraday/request/multipart.rb:13:in `call'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.5/lib/faraday/response.rb:8:in `call'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.5/lib/faraday/connection.rb:110:in `post'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/twitter-4.5.0/lib/twitter/request/multipart_with_file.rb:14:in `call'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.5/lib/faraday/connection.rb:245:in `run_request'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/faraday-0.8.5/lib/faraday/request/url_encoded.rb:14:in `call'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/lib/tasks/scheduler.rake:11:in `block in <top (required)>'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/twitter-4.5.0/lib/twitter/api/tweets.rb:129:in `update'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/twitter-4.5.0/lib/twitter.rb:52:in `method_missing'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/twitter-4.5.0/lib/twitter/api/utils.rb:82:in `object_from_response'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/twitter-4.5.0/lib/twitter/client.rb:81:in `request'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: /app/vendor/bundle/ruby/1.9.1/gems/twitter-4.5.0/lib/twitter/client.rb:70:in `post'
2013-02-11T19:00:39+00:00 app[scheduler.8796]: (See full trace by running task with --trace)
2013-02-11T19:00:39+00:00 app[scheduler.8796]: Tasks: TOP => tweet
2013-02-11T19:00:41+00:00 heroku[scheduler.8796]: Process exited with status 1

我怎样才能捕捉到这个特定的错误并重试推文直到它被发送？

在我的 rake 文件中：

task :tweet => :environment do
 if ApprovedTweet.all.size > 0
    t = ApprovedTweet.first
    Twitter.update(t.text)
    t.destroy
 end
4

1 回答 1

1

从Twitter gem 的文档中可以看出，这Twitter::Error::TooManyRequests似乎是您要捕获的错误。

如果我是你，我不会在发送之前重试发送推文（特别是在 rake 任务中 - 你很容易以僵尸进程结束），而是允许在失败之前进行多次重试：

begin     
  Twitter.update(t.text)
rescue Twitter::Error::TooManyRequests => e
  retries ||= 0
  retries +=  1
  if retries < ARBITRARY_MAX_RETRY_LIMIT
    # optionally sleep or delay for a while
    # ... or just log failure 
    retry
  else
    raise e # or another custom error of yours
  end
end
于 2013-02-11T20:58:09.850 回答