v2.2.2

What's Changed

• Updated redirected dependency by @jborlum in #60
• go mod stuff by @rubyist in #67

New Contributors

• @jborlum made their first contribution in #60

Full Changelog: v2.2.1...v2.2.2

v2.2.1

Merge pull request #44 from abferm/master

Fix issue #43 [Value alignment issue on 32-bit systems (ARM)]

Release 2.2.0

2.2.0 - 2016-08-09

Added

• Externally provided event listener channel (@spencerkimball)

Deprecated

• Nothing

Removed

• Nothing

Fixed

• Reduce allocations around last failure time storage
• Use the Clock for window code as well
• Remove test data race
• Fix race condition in state() (@tamird)

Release 2.1.7

Added

• Nothing

Deprecated

• Nothing

Removed

• Nothing

Fixed

• Set Backoff.MaxElapsedTime to 0 as default [@matope]
• Use a lock when modifying nextBackoff
• Fix goroutine leak when using timeouts [@isaldana]
• Fix window buckets that should be empty [@isaldana]
• Update backoff package, which has been renamed

Release 2.1.6

2.1.6 - 2016-02-02

Added

• Nothing

Deprecated

• Nothing

Removed

• Nothing

Fixed

• client.Do() was not returning the error when it timed out [@ryanmurf]

Release 2.1.5

2.1.5 - 2015-11-19

Added

• Nothing

Deprecated

• Nothing

Removed

• Nothing

Fixed

• Respect backoff.Stop [@bc-vincent-zhao]

Release 2.1.4

2.1.4 - 2015-09-01

Added

• Nothing

Deprecated

• Nothing

Removed

• Nothing

Fixed

• HTTP client was using a new panel object instead of the one it added the breaker to [@ryanmurf]

Release 2.1.3

2.1.3 - 2015-08-05

Added

• Configurable bucket time and number [@thraxil]
• Use mock clock for test [@andreas]

Deprecated

• Nothing

Removed

• Nothing

Fixed

• Bug in statsd bucket name documentation / example [@thraxil]

Release 2.1.2

Added

• Nothing

Deprecated

• Nothing

Removed

• Nothing

Fixed

• Simplify Call() for rate breaker, fixing a reset bug [@Melraidin]

Release 2.1.1

Added

• Nothing

Deprecated

• Nothing

Removed

• Nothing

Fixed

• Ensure the half opens counter resets when the breaker resets, or auto-resetting may not occur