Permalink
Commits on Nov 22, 2017
Commits on Jul 26, 2017
  1. 2.1.4

    fw42 committed Jul 26, 2017
  2. Merge pull request #107 from Shopify/rescue-econnrefused

    fw42 committed Jul 26, 2017
    Rescue Errno::ECONNREFUSED
  3. Rescue Errno::ECONNREFUSED

    fw42 committed Jul 26, 2017
Commits on Jul 6, 2017
  1. Update CHANGELOG.md

    andremedeiros committed Jul 6, 2017
  2. Bump to 2.1.3

    andremedeiros committed Jul 6, 2017
  3. Merge pull request #105 from Shopify/handle-exit-signals

    andremedeiros committed Jul 6, 2017
    Handle ThreadError on exit signal
  4. Eliminate unnecessary step

    andremedeiros committed Jul 6, 2017
  5. Assert socket is sent on exit

    andremedeiros committed Jul 6, 2017
  6. Handle ThreadError on exit signal

    andremedeiros committed Jul 6, 2017
Commits on Mar 23, 2017
  1. Put cleanup into ensure block

    kirs committed Mar 23, 2017
  2. Merge pull request #99 from Shopify/block-must-be-given

    kirs committed Mar 23, 2017
    Block must be given to assert_statsd_call
  3. Block must be given to assert_statsd_call

    kirs committed Mar 23, 2017
Commits on Dec 6, 2016
  1. Merge pull request #97 from Shopify/update_changelog

    wvanbergen committed Dec 6, 2016
    Release 2.1.2 & update changelog
  2. Bump version to 2.1.2

    wvanbergen committed Dec 6, 2016
  3. Update CHENGELOG.md

    wvanbergen committed Dec 6, 2016
Commits on Nov 25, 2016
  1. Merge pull request #96 from Shopify/make_travis_happy

    wvanbergen committed Nov 25, 2016
    Travis matrix tweaks
  2. Travis matrix tweaks

    wvanbergen committed Nov 25, 2016
  3. Merge pull request #95 from codegourmet/topic/rspec_matchers_improvem…

    wvanbergen committed Nov 25, 2016
    …ents
    
    Topic/rspec matchers improvements
Commits on Nov 24, 2016
  1. improved failed expectation message

    codegourmet committed Nov 24, 2016
    Since the matcher captures all statsd calls, it will now output why
    the expectation was unmatched.
    
    Example for matcher without :times option
    
        expected StatsD :sample_rate for metric 'counter' to be called
          at least once with: 0.5
          captured metrics: 0.3, 0.7
    
    Example for matcher with :times option:
    
        expected StatsD :value for metric 'counter' to be called
          exactly 2 times with: 1
          captured metrics: 1, 2
  2. fixed rspec matchers: :times with other expects

    codegourmet committed Nov 24, 2016
    When :times expectation option was combined with other expectation
    options, the matcher always succeeded. This was due to the .all?(:!=)
    statement in the matcher.
    
    The solution was to match the found metrics count which matched
    to the :times parameter (or allow for > 0 if no :times given).
Commits on Aug 15, 2016
  1. Merge pull request #92 from Shopify/sg-use-prepended-modules

    sgrif committed Aug 15, 2016
    Use prepended modules instead of modifying the target class
  2. Don't blow up when used with a module

    sgrif committed Aug 15, 2016
  3. Use prepended modules instead of modifying the target class

    sgrif committed Aug 15, 2016
    If the method being overidden by this gem is also overidden by a prepended
    module, the result ends up being infinite recursion as `old_method` will always
    be pointing to the method added by the module, and `super` there will point to
    the addition from `StatsD::Instrument`. Normally I would just prepend a single
    anonymous module every time this was called, but I've attempted to preserve the
    "has this already been instrumented" checks and the ability to remove
    instrumentations later. Instead we keep a hash of various modules, and
    define/undefine the method being overidden. It's impossible to remove a module
    after it's been added, but when `statsd_remove_measure` or friends are called
    we simply undefine the methdos on the module leaving us with an empty module
    doing nothing.
    
    This does mean that we'll end up with a lot of anonymous modules in the
    ancestors chain, but there's really no way to avoid that. I have given them a
    more descriptive name at least in order to aid debugging if that occurs
    
    Fixes #91.
Commits on Aug 9, 2016
  1. Merge pull request #90 from reprah/rails-environment

    wvanbergen committed Aug 9, 2016
    Ask Rails for the environment when Rails is loaded and not just defined
Commits on Jun 28, 2016
  1. Bump version to 2.1.1

    wvanbergen committed Jun 28, 2016
Commits on Jun 22, 2016
  1. Merge pull request #86 from Shopify/statsd-instrument-assertions-with…

    surrahman committed Jun 22, 2016
    …-more-options
    
    Support an ordered set of options when asserting statsd calls
Commits on Jun 21, 2016
  1. Revised StatsD::Instrument::Assertions to allow more options in #asse…

    surrahman committed May 27, 2016
    …rt_statsd_call
Commits on Jun 16, 2016
  1. Bump version to 2.1.0

    wvanbergen committed Jun 16, 2016
Commits on Jun 15, 2016
  1. Merge pull request #87 from Shopify/support_value_keyword_argument_fo…

    wvanbergen committed Jun 15, 2016
    …r_all_metric_types
    
    Support a value keyword argument for all metric types.
  2. Support a value keyword argument for all metric types.

    wvanbergen committed Jun 15, 2016
Commits on May 23, 2016
  1. Merge pull request #84 from shaneog/rspec-core

    wvanbergen committed May 23, 2016
    Use rspec-core instead of just rspec for rspec-rails compatibility