So We just spent a huge amount of time to properly filter out these kinds of messages using Raven’s shouldSendCallback only to find out it didn’t work. I looked at the Raven.js code (horrified BTW) and I’m willing to bet it is fundamentally broken.
Granted Ember should try to avoid false positive exceptions like TransisionAborted from reaching onerror but to be honest it really is the responsibility of the reporting library to know how to STFU and it is obvious Raven.js just isn’t up to the task.
I going to dive back into that swamp of code and see just why Raven is misbehaving. A filter should not be this difficult!