Next | Query returned 4 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2023-06-09 17:29:10 by Takahiro Kambe | Files touched by this commit (2) | Package updated
Log message:
www/ruby-faraday-retry: update to 2.2.0

2.2.0 (2023-06-01)

What's Changed

* Implement header_parser_block option by @zavan in #28

New Contributors

* @zavan made their first contribution in #28
   2023-03-05 15:29:26 by Takahiro Kambe | Files touched by this commit (2) | Package updated
Log message:
www/ruby-faraday-retry: update to 2.1.0

2.1.0 (2023-03-03)

What's Changed

* Add support for custom RateLimit headers. by @brookemckim in #13
* Fixes retry_block example in README. by @justinlittman in #12
* README: update link to the RateLimit RFC by @olleolleolle in #14
* docs: update link to RFC by @olleolleolle in #15
* Rubocop linting by @olleolleolle in #16
* style: disable Metrics/ClassLength by @olleolleolle in #17
* Adds Ruby 3.2 to the CI matrix by @petergoldstein in #18
* Typo fix :) by @adifsgaid in #19
* Introduce issue templates by @iMacTia in #22

New Contributors

* @justinlittman made their first contribution in #12
* @brookemckim made their first contribution in #13
* @petergoldstein made their first contribution in #18
* @adifsgaid made their first contribution in #19
   2023-01-09 13:57:32 by Takahiro Kambe | Files touched by this commit (2) | Package updated
Log message:
www/ruby-faraday-retry: update to 2.0.0

2.0.0 (2022-06-15)

What's Changed

* Retry block change by @jrochkind in #3
* Add support for the RateLimit-Reset header by @maxprokopiev in #9
* CI: Use new GitHub Action checkout@v3, and drop unused files by
  @olleolleolle in #10
   2023-01-07 16:25:34 by Takahiro Kambe | Files touched by this commit (4)
Log message:
www/ruby-faraday-retry: add package version 1.0.3

Required by newer ruby-faraday package.

Faraday Retry

The Retry middleware automatically retries requests that fail due to
intermittent client or server errors (such as network hiccups).

By default, it retries 2 times and handles only timeout exceptions.

It can be configured with an arbitrary number of retries, a list of
exceptions to handle, a retry interval, a percentage of randomness to add to
the retry interval, and a backoff factor.

The middleware can also handle the Retry-After header automatically when
configured with the right status codes (see below for an example).

Next | Query returned 4 messages, browsing 1 to 10 | previous