Closed alexbarcelo closed 4 years ago
Currently, a newVersion call ends up in the DataService (java) trying to deserialize the object.
If the object is a Python DataClayObject, this makes the call to fail.
Following the current architecture, those calls should be directed to the Python ExecutionEnvironment.
Badly reported bug, that was not the case. I misread some stack trace and methods and ended up troubleshooting ghosts.
Currently, a newVersion call ends up in the DataService (java) trying to deserialize the object.
If the object is a Python DataClayObject, this makes the call to fail.
Following the current architecture, those calls should be directed to the Python ExecutionEnvironment.