Open lbolla opened 5 years ago
@lbolla When is this going to be done? Isn't this a one-line fix? Does this product even work?
File "/usr/local/lib/python3.6/site-packages/raven/utils/json.py", line 63, in dumps\n return json.dumps(value, cls=BetterJSONEncoder, **kwargs)\n File "/usr/local/lib/python3.6/json/__init__.py", line 238, in dumps\n **kw).encode(obj)\nTypeError: __init__() got an unexpected keyword argument \'encoding\'\n'
@ohimors I've already submitted a PR ages ago: https://github.com/getsentry/raven-python/pull/1350 But I've since moved to use the new "Sentry SDK", given that "raven-python" is deprecated. I don't know if the maintainers are actively working on Raven anymore.
I'll look into this on Monday. We still want to fix bugs in Raven.
()
-keys is clouded by this error, but it's not inherently broken under Python 2.skip_keys
. It's way too broad in how it operates and discarding is not the way to go.raven.serializers.base.DictSerializer
. I wonder why this is not applied in this case.
See comment https://github.com/getsentry/raven-python/issues/1155#issuecomment-473423879
When serializing error data (traceback, local vars, etc.) to be sent to the backend,
json.dumps
is used, inraven.utils.json
.json.dumps
can fail, e.g. when local data has the form:which cannot be serialized to json (because of the tuple key). By using
json.dumps(skipkeys=True)
these kind of keys will be ignored.