[#66678] [ruby-trunk - Feature #10481] Add "if" and "unless" clauses to rescue statements — alex@...
Issue #10481 has been updated by Alex Boyd.
3 messages
2014/12/04
[#66762] Re: [ruby-changes:36667] normal:r48748 (trunk): struct: avoid all O(n) behavior on access — Tanaka Akira <akr@...>
2014-12-10 0:44 GMT+09:00 normal <ko1@atdot.net>:
3 messages
2014/12/10
[#66851] [ruby-trunk - Feature #10585] struct: speedup struct.attr = v for first 10 attributes and struct[:attr] for big structs — funny.falcon@...
Issue #10585 has been updated by Yura Sokolov.
3 messages
2014/12/15
[#67126] Ruby 2.2.0 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 2.2.0.
8 messages
2014/12/25
[#67128] Re: Ruby 2.2.0 Released
— Rodrigo Rosenfeld Rosas <rr.rosas@...>
2014/12/25
I can't install it in any of our Ubuntu servers using rbenv:
[#67129] Re: Ruby 2.2.0 Released
— SHIBATA Hiroshi <shibata.hiroshi@...>
2014/12/25
> I can't install it in any of our Ubuntu servers using rbenv:
[ruby-core:67206] [ruby-trunk - Feature #10674] [Open] Net::HTTP retries idempotent requests once after a timeout, but its not configurable
From:
jeremy.lecour@...
Date:
2014-12-29 15:10:53 UTC
List:
ruby-core #67206
Issue #10674 has been reported by Jテゥrテゥmy Lecour. ---------------------------------------- Feature #10674: Net::HTTP retries idempotent requests once after a timeout, but its not configurable https://bugs.ruby-lang.org/issues/10674 * Author: Jテゥrテゥmy Lecour * Status: Open * Priority: Normal * Assignee: Eric Hodel * Category: * Target version: ---------------------------------------- Hi, I've noticed that Net::HTTP retries idempotent requests once after a time-out. It seems to adhere to the RFC 2616 (http://tools.ietf.org/html/rfc2616), but it is not always the best thing to do. When you don't know exactly how a remote web service works, it may be wise to retry after a time-out. But when you know that a retry won't change anything, it should be possible to disable this automatic retry. Otherwise, the server will have to deal with 2 requests (instead of 1) and the client will effectively time-out twice later than expected (time for the first and second time-out). Having a basic "#retry=" (like we have "#read_timeout=" or "#open_timeout" would be good first step. The value could be a simple boolean, or even an integer for the maximum number of retries. The "Retry" middleware in Faraday has a more comprehensive feature set with max retries, exponential back-off, 窶ヲ : https://github.com/lostisland/faraday/blob/master/lib/faraday/request/retry.rb -- https://bugs.ruby-lang.org/