-
Notifications
You must be signed in to change notification settings - Fork 202
adding a Python3 fix to JsonRPC serializer #418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
adding a Python3 fix to JsonRPC serializer #418
Conversation
|
Very strange fix. When your right that's not working right now, but tests says isn't this. |
|
There were no tests for JsonRPC I think |
|
It’s wrong |
|
@cloud-rocket please give an example code which reproduces error. |
|
I am working on tests and the following code reproduces the error: This code works with my fix. But my fix is not dealing with the case when an exception is thrown. So the fix is only partly solving the problem. Trying to find what's wrong with the exception serialization.... |
42cd02d to
38a80dc
Compare
|
Everything fixed (including exception handling) and tests are added. |
4060132 to
f1f7623
Compare
f1f7623 to
998d00e
Compare
|
Why this PR is ignored? |
|
@cloud-rocket why have the fallen tests have been ignored? |
5c92d10 to
f8337e9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a bad job, thanks for writing the tests, and code style in general LGTM, but I have to demand changes because it's completely unsafe.
f8337e9 to
5a205e3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cloud-rocket, I like what is happening, I have left a few wishes, and I hope they will be taken into consideration.
5a205e3 to
6c52e19
Compare
|
Are you open to consider this version of I found myself anyway using it, because known exceptions are easier to handle and there is no vulnerability here as far as I understand. |
|
@mosquito, if this PR is OK, would you merge it, because right now we have to make nasty tricks to make this functionality work. |
|
@screech since bump |
JsonRPC is throwing and error
encoding error "string argument without an encoding"without this fix.It's probably a leftover from Python 2