[1.2.0] Each plugin sends separate mesage on same error

[devel-pa]

Hi,
I'm testing your library on a backbone stack and I added
https://cdn.ravenjs.com/1.2.0/backbone,jquery,native/raven.js
I have 4 server calls with the same callstack.

Thanks,
Paul

[mattrobenolt]

Hmm, could you provide some more information here? I'm not sure why we'd be sending 4 identical messages, if that's what you're suggesting.

Can you provide a link to these in getsentry.com or send over the raw data packets that are being sent?

[devel-pa]

I have no sentry account, just testing how it's working for a possible integration. As for data I have to ask my superiors.

The exception looks like this:
"exception": { "type": "TypeError", "value": "line.hasValues is not a function" },
If what I can provide is not enough let's close the issue.

Thanks

[mattrobenolt]

Yeah, that's not enough information to debug, but I'll leave this ticket open since it's apparently an outstanding issue that I don't want to ignore.

If you can share more information, that'd be great or could put together something that reproduces that we could take a look at.

Thanks for the report. :) It's much appreciated.

[hermansje]

I noticed the same behaviour with Raven 2.1.0: each plugin posts to Sentry, so errors that pass through multiple plugins, are sent multiple times.
I made a plunk to demonstrate this with the angular and console plugins:
http://plnkr.co/edit/5GfQus0IcdAmrkBTYiC9?p=preview

[benvinegar]

@hermansje – in this example, you are using both the Angular and console plugins. Angular logs errors onto console.error, which is what causes Raven.js to pick it up a second time via the console plugin.

Also, the error is technically different, because only the first report contains a stack trace. The second doesn't have a trace because it is just being logged via captureMessage (via the console plugin). I don't consider this a bug; just a quirk of Angular that doesn't play nicely with the console plugin. At best, it is a separate issue.

Closing this ticket because the original submitter did not provide example code, and I don't think this example qualifies.