Sentry-javascript: Errors reported as '<no message value>'

Created on 28 Feb 2013 · 8Comments · Source: getsentry/sentry-javascript

See: https://github.com/getsentry/sentry/blob/master/src/sentry/coreapi.py#L300

/cc @jeremyhaile

Source

mattrobenolt

All 8 comments

So this message is coming from Sentry itself. raven-js isn't sending it. See: https://github.com/getsentry/sentry/blob/master/src/sentry/coreapi.py#L300

That's the reason why you can't hide it with ignoreErrors.

The issue is why that condition is happening in the first place.

mattrobenolt on 28 Feb 2013

Yes - I've also updated ignoreErrors to ignore errors '' and null, but I'm still getting on the server side. Also, there is no stack trace or location with these errors.It also occurs in IE, Chrome, Safari and Firefox.

I've temporarily made this event public in the interest of solving the mystery: https://app.getsentry.com/sideqik/sideqik/group/3377745/

Please let me know if that helps you in any way - as I'd like to make it private again once you take a look.

jeremyhaile on 28 Feb 2013

I'm seeing this too -- https://app.getsentry.com/id/id/group/4714283/.

jfirebaugh on 16 Apr 2013

I still get tons of these errors. I wish I could ignore them.

jeremyhaile on 16 Apr 2013

Any update on this?

uglymunky on 22 Oct 2013

@uglymunkey, check out 03d8925. I haven't been able to actually reproduce this on my own, but we'll see if that works.

mattrobenolt on 22 Oct 2013

cool, thanks.

uglymunky on 23 Oct 2013

I've been seeing this in spades lately. I suspected it was because I'm on Sentry 8.4, but RavenJS 1.1.16. I know, I know, I'm working on upgrading!

https://github.com/getsentry/raven-js/commit/03d8925c74b70b7cfcd7ea64dc741ce4d8c7844d is in 1.1.16 though, so I'm not sure why I'm seeing it.

Whatever the cause, I haven't been able to reproduce it either, but I do have 374k events which I'm happy to share if any further debugging is needed.