Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors reported as '<no message value>' #76

Closed
mattrobenolt opened this issue Feb 28, 2013 · 8 comments
Closed

Errors reported as '<no message value>' #76

mattrobenolt opened this issue Feb 28, 2013 · 8 comments

Comments

@mattrobenolt
Copy link
Contributor

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

/cc @jeremyhaile

@mattrobenolt
Copy link
Contributor Author

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.

@jeremyhaile
Copy link

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.

@jfirebaugh
Copy link

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

@jeremyhaile
Copy link

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

@gxxcastillo
Copy link

Any update on this?

@mattrobenolt
Copy link
Contributor Author

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

@gxxcastillo
Copy link

cool, thanks.

@mwcz
Copy link
Contributor

mwcz commented May 11, 2016

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!

03d8925 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants