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

Concurrency Testing For Remove right after an Insert. #36

Closed
theodorDiaconu opened this issue Nov 16, 2016 · 1 comment
Closed

Concurrency Testing For Remove right after an Insert. #36

theodorDiaconu opened this issue Nov 16, 2016 · 1 comment
Labels
THINK!

Comments

@theodorDiaconu
Copy link
Contributor

theodorDiaconu commented Nov 16, 2016 •
edited

In the tests sometimes remove wasn't showing up, the logs looked good, maybe dispatchjs:phantom somehow closes the connection (?), I really am clueless. Investigate what was going on.
@theodorDiaconu
Copy link
Contributor Author

The problem was that things happened so fast, that if you do an insert and remove after, no data is pushed to the client (no remove and no add). I assume this is due to Mergebox. And it proves that the code is efficient and consistent. If we did a setTimeout of 100ms it worked everytime.

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

No branches or pull requests
1 participant
@theodorDiaconu