RayGun appears to call str() on all locals in a stack trace before sending an exception off to their server, which breaks when one of those locals are unicode and need to be encoded. We currently have RayGun disabled as a workaround. I believe the solution would be to submit a PR to their Python library that casts the locals with unicode() instead of str(), but more testing of that is necessary.
Someone already reported this to Raygun: https://github.com/MindscapeHQ/raygun4py/issues/23 I've submitted a PR to their library: https://github.com/MindscapeHQ/raygun4py/pull/24
Assignee: nobody → mkelly
Commit pushed to master at https://github.com/mozilla/pontoon https://github.com/mozilla/pontoon/commit/0a491ff77aeea8b121d4288e746995ccec785ec9 Bug 1179963: Re-enable raygun and use fork. Re-enables Raygun and temporarily uses my fork of raygun4py with a fix for our unicode issues. Once the fix gets merged we should switch back to the official library.
Only remaining step here is to switch back to using the default RayGun library once our two current PRs are merged upstream.
Commit pushed to master at https://github.com/mozilla/pontoon https://github.com/mozilla/pontoon/commit/a4f92b3d4a56e98bedb1bfe519f718875b539067 Fix bug 1179963: switch back to default RayGun lib (#390)
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Commit pushed to master at https://github.com/mozilla/pontoon https://github.com/mozilla/pontoon/commit/b6415bf23e3bb7002838a0a54a059cd2d21112fd Bug 1179963: Use new Raygun API
You need to log in before you can comment on or make changes to this bug.