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

multiprocessing fails in windows - cannot pickle thread.lock #20

Closed
int3ll3ct opened this issue Mar 11, 2017 · 1 comment
Closed

multiprocessing fails in windows - cannot pickle thread.lock #20

int3ll3ct opened this issue Mar 11, 2017 · 1 comment
Assignees
@int3ll3ct
Labels
bug

Comments

@int3ll3ct
Copy link
Collaborator

During Openroast 1.2 development, I have assessed that v0.2.0 still fails to operate in a windows cx_Freeze application, as well as from a standard python windows install (as a non-msi, non-frozen python app).

This is because auto_connect() spawns a thread to try to repeatedly connect to hardware, and when the hardware is found, two processes are started. Starting the processes in Windows forces a pickle of the freshroastsr700 object instance, which now has an active thread running (the auto_connect thread), which cannot be pickled.

I have a workaround that I am developing in a v0.2.1 branch for eventual submission.
@int3ll3ct int3ll3ct added the bug label Mar 11, 2017
@int3ll3ct int3ll3ct self-assigned this Mar 11, 2017
int3ll3ct pushed a commit that referenced this issue Mar 11, 2017
Attempting to resolve issue #20. Works in Linux, need to test on Wind…
4faa6e7 
…ows next.
int3ll3ct pushed a commit that referenced this issue Mar 12, 2017
Confirmed that these code changes resolve issue #20 on Windows 10 64-…
ee8a784 
…bit systems.
@int3ll3ct int3ll3ct mentioned this issue Mar 12, 2017
Merged
@int3ll3ct
Copy link
Collaborator Author

Fixed in v0.2.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@int3ll3ct int3ll3ct

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@int3ll3ct