Skip to content
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

[QUESTION] FugueWorkflowResult & pickle deserialization #470

Open
bitsofinfo opened this issue May 17, 2023 · 2 comments
Open

[QUESTION] FugueWorkflowResult & pickle deserialization #470

bitsofinfo opened this issue May 17, 2023 · 2 comments

Comments

@bitsofinfo
Copy link
Contributor

bitsofinfo commented May 17, 2023

anyone else doing anything that pickles FugueWorkflowResult ? I'm executing some sql flows over secondary python processes, and running into an error like

return _ForkingPickler.loads(buf.getbuffer())
TypeError: FugueWorkflowResult.__init__() missing 1 required positional argument: 'yields'

i assume this is because FugueWorkflowResult doesn't have provide a no-arg constructor? (not sure actually, not familiar w/ pickle but this smells like a deserialization kind of issue w/ a class not being able to be rematerialized)

I'm getting around this by capturing the result and just extracting the yields and returning that instead prior to being pickled and sent back to the parent process.

@goodwanghan
Copy link
Collaborator

Fugue doesn't support running the main(driver) logic on different processes. So the behavior is undefined.

@bitsofinfo
Copy link
Contributor Author

interestingly enough this error went away when I switched to a different multiprocessing framework that sits above python's. I started using pebble. In any case, this use-case is most definitely one I am pursuing and is currently working for me. i.e. a primary process forking off child processes where the actual fugue sql flows get executed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants