16 Nov, 2011
1 commit
02 Nov, 2011
2 commits
-
Conflicts: Gemfile.lock
-
Async confirm
26 Oct, 2011
1 commit
24 Oct, 2011
1 commit
20 Oct, 2011
1 commit
19 Oct, 2011
1 commit
18 Oct, 2011
1 commit
15 Oct, 2011
1 commit
09 Oct, 2011
2 commits
08 Oct, 2011
1 commit
27 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
16 Sep, 2011
1 commit
-
…ixes misc. problems for both rake tasks and production servers. (smtp setttings were previously not being passed through in Rake tasks)
13 Sep, 2011
3 commits
-
…:Base.smtp_settings needed to be set, not Errbit::Application.config.action_mailer.smtp_settings.
11 Sep, 2011
1 commit
-
…tylesheets. Module is small enough to live in initializer.
10 Sep, 2011
1 commit
09 Sep, 2011
1 commit
06 Sep, 2011
2 commits
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.
04 Sep, 2011
1 commit
-
…e-added full backtrace, as well as including the 'app_backtrace' in the WHERE section.
02 Sep, 2011
3 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.
-
…s missing on a standard deployment
01 Sep, 2011
3 commits
27 Aug, 2011
2 commits
19 Aug, 2011
2 commits
-
…ntroller into their respective models. * Wrote specs for Fogbugz. Turns out that the Fogbugz API used the 'Crack' gem which happened to break mongoid by playing with the String class. See here for details: [ https://github.com/mongoid/mongoid/issues/618 ]. * This is why I had to upgrade mongoid to version 2.1.1, which included the 'Crack' fix. Upgrading Mongoid to 2.1.1 required the following changes: ** Fixing a counter_cache test on Err model ** Namespacing all of the subclassed IssueTracker models based on their parent directory ** Setting `config.mongoid.preload_models = true` in config/application.rb
15 Aug, 2011
1 commit
-
…e by default, but this can be changed in config.yml [ci skip]