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

Ming objects are not synchonized on multithreaded environments #5

Open
ipazc opened this issue Oct 3, 2017 · 1 comment
Open

Ming objects are not synchonized on multithreaded environments #5

ipazc opened this issue Oct 3, 2017 · 1 comment
Assignees
@ipazc
Labels
bug

Comments

@ipazc
Copy link
Owner

ipazc commented Oct 3, 2017

When updating the same object twice in small amounts of time, the first object changes are not reflected in the second object. This needs a layer of synchronization.
@ipazc ipazc self-assigned this Oct 3, 2017
@ipazc ipazc added the bug label Oct 3, 2017
@ipazc
Copy link
Owner Author

ipazc commented Oct 11, 2017

Confirmed: when dealing with gunicorn workers, some workers override the modification done by others to the dataset.

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

@ipazc ipazc

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ipazc