06 Mar, 2013
1 commit
28 Jan, 2013
1 commit
05 Nov, 2012
1 commit
04 Oct, 2012
1 commit
-
…tification service, or authentication provider
19 Sep, 2012
2 commits
-
Conflicts: lib/tasks/errbit/database.rake
11 Sep, 2012
2 commits
03 Sep, 2012
1 commit
26 Aug, 2012
2 commits
06 Jun, 2012
1 commit
-
looks like this mongoid bug was fixed here: https://github.com/mongoid/mongoid/commit/2b7407977452a1f05d6eb5edf2d9a00b0c359ccf
03 Jun, 2012
1 commit
01 Jun, 2012
2 commits
30 May, 2012
1 commit
28 May, 2012
2 commits
-
This allows us to know who took the action that caused the error, so we can follow up via email or phone if we need further information about the context.
21 May, 2012
1 commit
09 May, 2012
1 commit
06 Apr, 2012
1 commit
02 Feb, 2012
1 commit
-
…onger used in the project)
01 Feb, 2012
1 commit
-
…key' for :klass field.)
20 Dec, 2011
1 commit
18 Nov, 2011
1 commit
-
that. Also improve the message for ApiVersionError.
19 Oct, 2011
1 commit
-
v2.0 API and the Airbrake v2.2 API.
29 Sep, 2011
1 commit
26 Sep, 2011
2 commits
-
…les, fixed whitespace, upgraded RSpec to 2.6.0 Conflicts: app/helpers/errs_helper.rb app/mailers/mailer.rb app/models/notice.rb app/views/errs/_table.html.haml app/views/errs/show.html.haml app/views/notices/_summary.html.haml spec/models/issue_trackers/redmine_tracker_spec.rb spec/views/errs/show.html.haml_spec.rb
13 Sep, 2011
1 commit
11 Sep, 2011
1 commit
-
…tylesheets. Module is small enough to live in initializer.
05 Sep, 2011
4 commits
-
concerns (e.g. fingerprint) from notice parsing concerns. This also makes it easier to support multiple versions of the Airbrake API.
-
…okogiri which is already in use (as opposed to hpricot). Required InlineCss module on all mailers. Moved email styles into public/stylesheets/email.css
04 Sep, 2011
1 commit
-
…e-added full backtrace, as well as including the 'app_backtrace' in the WHERE section.
02 Sep, 2011
2 commits
-
… are now stored in an automatically created app called 'Self.Errbit'.
-
… them locally, in an automatically created App named "Self.Errbit". Errbit can still be configured to send errors to our central Errbit instance, but we were getting too many spam errors caused by users (e.g. invalid email address). Most developers will prefer to see Errbit's errors themselves anyway. I will write up a HowTo on how developers can configure a GitHub issue tracker for 'Self.Errbit', in order to send us error reports.
01 Sep, 2011
2 commits
-
…or heroku users using the free database. [ci skip]
-
…s together in tasks/database.rake [ci skip]