-
Notifications
You must be signed in to change notification settings - Fork 19
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
[Gateway] insecure string pickle #280
Comments
Do you have any other details on this. Was this a robot, or was it the concert? Did it happen on startup, runtime or on shutdown? |
It was on the robot,and runtime. The concert was up and running more than 5mins. Though it happened, public interface connections didn't get broke and were able to receive all commands. |
Yeah, it would bring down the gateway node, but all existing socket connections would remain. |
Happened in the robot.
|
According to http://stackoverflow.com/questions/1746825/python-valueerror-insecure-string-pickle, it's probably a corrupted pickle. We should catch this error, and discard the original request being deserialized. |
Do you have any suggestion to chase up this issue? where would be the best place to start to add debug message? |
I don't have a particularly good solution for this problem.
|
Another log
|
Looking at the three different logs, insecure string pickle error raised while deserializing flip_in request in all cases. Thus, flip_ins keys in hub is corrupted probably. |
The text was updated successfully, but these errors were encountered: