-
Notifications
You must be signed in to change notification settings - Fork 50
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
in-memory queue is broken #31
Comments
peter-wangxu
added a commit
that referenced
this issue
Nov 1, 2017
When share in-memory queue in multi-thread, the queue is not properly synced between threads, this commit uses shared-cache to achive the synchronization. fixes #31
peter-wangxu
added a commit
that referenced
this issue
Nov 1, 2017
When share in-memory queue in multi-thread, the queue is not properly synced between threads, this commit uses shared-cache to achive the synchronization. fixes #31
peter-wangxu
added a commit
that referenced
this issue
Nov 1, 2017
When share in-memory queue in multi-thread, the queue is not properly synced between threads, this commit uses shared-cache to achive the synchronization. fixes #31
peter-wangxu
added a commit
that referenced
this issue
Nov 1, 2017
When share in-memory queue in multi-thread, the queue is not properly synced between threads, this commit uses shared-cache to achive the synchronization. fixes #31
peter-wangxu
added a commit
that referenced
this issue
Nov 1, 2017
When share in-memory queue in multi-thread, the queue is not properly synced between threads, this commit uses shared-cache to achieve the synchronization. fixes #31
peter-wangxu
added a commit
that referenced
this issue
Nov 4, 2017
When share in-memory queue in multi-thread, the queue is not properly synced between threads, this commit uses shared-cache to achieve the synchronization. fixes #31
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the multi-threading tests are consistently crash the python when using memory queue.
Need investigate.
The text was updated successfully, but these errors were encountered: