-
Notifications
You must be signed in to change notification settings - Fork 9
kombu.exceptions.ContentDisallowed: Refusing to deserialize disabled content of type pickle (application/x-python-serialize) #32
Comments
@femtotrader, what callme version do you use? |
@skudriashev Sorry that wasn't github version... I git clone and python setup.py install |
@femtotrader, we discussed this with @ceelian several times. First question - why do you really need json, why not to use pickle? Is there any cases that would require json. Second, how would you work with exceptions from remote end. AFAIK, they are currently pickled and delivered to the client side. @ceelian, can give more detail on that. |
@ceelian @skudriashev It's a quite complicated use case. My Python script need to send JSON RPC to a database where an other software (not Python) is able to execute it. I just want to use messaging to be able to send JSON RPC in any language. My first idea was to do it myself so I did some RPC example with Pika (RabbitMQ) and I found after doing this callme which seems to be interesting (and probably much more professional than my ugly code - see below). About exception... JSON RPC provide error code -32600. We can also use an other error code and use traceback to output exception message to JSON RPC response
|
@femtotrader, does your implementation work as intended? |
Yes it works nearly as expected (timeout on server side is still missing but I can live without this feature for now) but I would prefer |
@femtotrader, supporting json-serializer means handling exceptions in different ways for different serializers, that I don't really like. |
Can't we have an abstract class (with same interface as my |
@femtotrader, I mean that currently you can do:
You are able to 'catch' remote exception locally. How it would be with json? |
Exception is raised in my |
@femtotrader, in your code you raise |
@femtotrader, any updates on this? :) |
see arskom/spyne#374 |
@femtotrader, spyne.io might be what you need, since raising error code is not the same like rising exception object from remote side. Since this issue header is not related to what we discussed here I'm cosing it. |
it's raising exception (inherited from |
Hello,
Kombu seems to disallow pickled objects.
I think they did it for security reason (should we care?)
How can I enable it ?
Is there a way to urge callme to use JSON RPC instead ?
Kind regards
The text was updated successfully, but these errors were encountered: