-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update the cloudpickling, possibly put into dill #2
Comments
I tested multyvac with our new "cloudpickle" module instead of the one in "util" and it fails. Currently looking into it but there are lots of differences between the two.
|
Update: server side, we try to import "cloudpickle.cloudpickle"
References to this module come from "_fill_function" and "_make_skel_func".
Now we would want to see why the actual pickling fails. Edit: could the root cause be #5 ? |
Even with the right 'cloudpickle.cloudpickle' import in the docker container, cloudpickle (git version) having been installed in the docker container, we still mysteriously fail client side with the error "multyvac.multyvac.RequestError: Could not parse body." No exception server side. |
Since
cloud
is no longer maintained and folks want thecloudpickle
, we should extract it out intodill
or a separate library.Example usage: ipython/ipython#5718
The text was updated successfully, but these errors were encountered: