JSON encoding fails to handle Django lazy objects

[acdha]

I've had a few errors which were not reported because Raven failed to JSON encode the data:

  File "/opt/mysite/.virtualenv/lib/python2.6/site-packages/simplejson/encoder.py", line 311, in iterencode
    return _iterencode(o, 0)
  File "/opt/mysite/.virtualenv/lib/python2.6/site-packages/raven/utils/json.py", line 22, in default
    return super(BetterJSONEncoder, self).default(obj)
  File "/opt/mysite/.virtualenv/lib/python2.6/site-packages/simplejson/encoder.py", line 213, in default
    raise TypeError(repr(o) + " is not JSON serializable")
TypeError: <django.utils.functional.__proxy__ object at 0x7fec99bd4110> is not JSON serializable

I'll try to get a debugger going to see exactly what the object in question is.

[aknapp]

We are running into this same issue with some errors that aren't getting logged to Sentry.

[acdha]

@aknapp: do you know what type of objects the original values are? I'm wondering how to cleanly handle this and it gets a bit hairier if the results aren't necessarily unicode.

[dcramer]

What version of Raven are you seeing this in?

David Cramer

twitter.com/zeeg
disqus.com/zeeg

On Tuesday, September 18, 2012 at 11:26 AM, Chris Adams wrote:

@aknapp (https://github.com/aknapp): do you know what type of objects the original values are? I'm wondering how to cleanly handle this and it gets a bit hairier if the results aren't necessarily unicode.

—
Reply to this email directly or view it on GitHub (#180 (comment)).

[acdha]

@dcramer: 2.0.5

[aknapp]

@dcramer: raven==2.0.3

[dcramer]

Upgrade to 2.0.6 and it should solve the problem. We specifically addressed a bug with Promise objects between 2.0.5 and 2.0.6

David Cramer

twitter.com/zeeg
disqus.com/zeeg

On Tuesday, September 18, 2012 at 11:37 AM, Andrew Knapp wrote:

@dcramer (https://github.com/dcramer): raven==2.0.3

—
Reply to this email directly or view it on GitHub (#180 (comment)).

[acdha]

I was just deploying 2.0.6 after your question

[aknapp]

Just upgraded to 2.0.6, will let you guys know if I see it again.

[dcramer]

Go ahead and reopen if you see this again, but it should be fixed