13 Oct, 2015

1 commit


12 Oct, 2015

7 commits


03 Oct, 2015

1 commit


15 Jul, 2015

1 commit


10 Apr, 2015

1 commit


11 Feb, 2015

1 commit


28 Jan, 2015

1 commit

  • - create configurator lib / specs / yardoc
    - update readme with env config instructions
    - create configuration docs, documenting all configs
    - remove copy_configs from rake errbit:bootstrap
    - set defaults environment variables in .env.default
    - remove mongoid example yaml configs
    Stephen Crosby
     

21 Jan, 2015

3 commits


20 Jan, 2015

2 commits

  • This change allow errbit to accept v3 api calls from airbrake ruby client
    and propably some other clients that I've no idea of. This is tiny change
    but it took me some time to investigate this, so I want to explain how
    to set everything up.
    
    It appears that there is a bug in airbrake gem that causes airbrake to not
    send api key in the request. The only way around this is to set project_id
    to the value of api key. I've opened an issue for this.
    
    https://github.com/airbrake/airbrake/issues/364
    
    To test it you need to add project_id option to airbrake initializer and also
    monkey patch Aibrake::Sender class. Airbrake uses v3 api only when host
    is set to collect.airbrake.io and project id is present.
    
    Your airbrake initializer should looks like this:
    
    Airbrake.configure do |config|
      config.api_key    = ENV['airbrake_api_key']
      config.host       = ENV['airbrake_host']
      config.port       = ENV['airbrake_port'].to_i
      config.project_id = ENV['airbrake_api_key']
      config.secure     = false
    end
    
    class Airbrake::Sender
      def json_api_enabled?
        true
      end
    end
    Michał Młoźniak
     
  • Stephen Crosby
     

18 Jan, 2015

1 commit


14 Nov, 2014

1 commit


21 May, 2014

1 commit


04 Nov, 2013

2 commits


19 Oct, 2013

1 commit


17 Oct, 2013

1 commit


01 Oct, 2013

1 commit


19 Sep, 2013

1 commit


08 Jul, 2013

1 commit


31 May, 2013

1 commit


22 May, 2013

1 commit


06 May, 2013

1 commit


05 May, 2013

2 commits


21 Mar, 2013

1 commit

  • <var> tags with blank values were ending up completely wrong in the
    resulting hash.
    
    This: (a user with a blank name)
        <var key="user">
           <var key="id">123</var>
           <var key="name"/>
        </var>
    
    Gets parsed by hoptoad_notifier into this:
        {
           'key' => 'user',
           'var' => [{
                 'key' => 'id',
                 '__content__' => '123'
              },{
                 'key' => 'name'
              }]
        }
    
    Which when passed through the "rekey" method, ended up like this:
        {
           'user' => {
              'id' => '123',
              'key' => 'name' # bad and wrong
           }
        }
    
    Now, after these changes, it correctly comes through as:
        {
           'user' => {
              'id' => '123',
              'name' => nil # much better!
           }
        }
    Daniel Beardsley
     

06 Mar, 2013

1 commit


28 Jan, 2013

1 commit


05 Nov, 2012

1 commit


04 Oct, 2012

1 commit


19 Sep, 2012

2 commits