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.

Sign up for GitHub

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

Jump to bottom

ProcessPool.callRemote Deferred sometimes fires with None instead of result #13

Open
moshez opened this issue Dec 14, 2017 · 1 comment
Open

ProcessPool.callRemote Deferred sometimes fires with None instead of result #13

moshez opened this issue Dec 14, 2017 · 1 comment

Comments

@moshez
Copy link
Contributor

moshez commented Dec 14, 2017

This is a weird behavior I ran into when issuing a new job from an errback on an earlier job. The attached illustrates better than I can do in English. The expected result is to see a result of {}, though, since that is what the "Fast" command in the worker returns. Instead, the result is None.
@heyakyra
Copy link

The attached

What attached?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@moshez @heyakyra