-
Notifications
You must be signed in to change notification settings - Fork 155
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
Support Scala closure serialization #299
Comments
What version of kryo and scala are you using. This should work. we do it all the time in scalding. |
Actually it isn’t magic. Not everything can be serialized (things like Threads or file handles for instance). I have found that test frameworks often have such things and your example seems to capture one. I am not surprised this does not work. |
I'll post here the same update I did on SO. Perhaps I should clarify the actual use case that is running into this issue to provide more context. The function is a callback from Akka HTTP route like the following:
The handler actor persists the request until it gets a response. It may take more than one response to construct the final output. I did some digging and it appears that the callback implementation is a CallbackRunnable. |
Can you post also the version of chill you were using and the scala version (2.11, 2.12?) |
chill-akka_2.12:0.9.2, Scala 2.12.4. I've since reverted that code, so you won't find it in the project I linked above. |
See https://stackoverflow.com/q/47806670/839733 for details
The text was updated successfully, but these errors were encountered: