Closed aselder closed 8 years ago
Looking at the code both the render?
and to_s
methods will blow up if the sql contains invalid UTF-8 characters
@aselder can you try locking your gem to github: 'honeybadger-io/honeybadger-ruby'
and re-run your tests to confirm that 1d5f137d0135322cac0224bc5e0be78015850001 fixes this for you?
@joshuap Will do, give me about an hour
@joshuap It looks good to me
Great, thanks! Working on a release.
2.3.1 has been released.
where Video is an ActiveRecord model and handle is a column on video returns
nil
if HoneyBadger NOT installed raises ArgumentError if HoneyBadger installedThis is actually an exception in the course of rescuing another exception. Using the debugger, the original exception is:
ActiveRecord::StatementInvalid: "ArgumentError: invalid byte sequence in UTF-8: SELECT videos.* FROM videos WHERE videos.handle = '\xB2\\\xCE>\\Z\x8Aa\u001D' LIMIT 1"
I realize that we shouldn't be constructing strings that are not invalid UTF-8, however there are cases where we have parameters that are encoded, and if changed can decode to invalid UTF-8. Still, installing the HoneyBadger gem shouldn't cause errors in cases where the base rails app doesn't