Closed Bug 1179963 Opened 9 years ago Closed 8 years ago

RayGun fails to capture exceptions when stack trace locals have unicode

Categories

(Webtools Graveyard :: Pontoon, defect, P5)

defect

Tracking

(firefox42 affected)

RESOLVED FIXED
Tracking Status
firefox42 --- affected

People

(Reporter: osmose, Unassigned)

Details

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.
Priority: -- → P5
Assignee: mkelly → nobody
Only remaining step here is to switch back to using the default RayGun library once our two current PRs are merged upstream.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.