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.

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

Race condition when synchronizing user lists #33

Open
dpp-gerrit opened this issue Jul 17, 2012 · 0 comments
Open

Race condition when synchronizing user lists #33

dpp-gerrit opened this issue Jul 17, 2012 · 0 comments
Labels
Aspect: Consistency Issue with Saros' consistency handling

Comments

@dpp-gerrit
Copy link

Host: A
Client: B
Client: C
Client: D

D invites E

First bug: The host does not know anything as long as D has not synchronized the user lists, but E does !

Second bug:

Instead of D, A invites E

While synchronizing the user lists, following can happen:

A tells E that B,C and D are part of the session. E now may send an activity to B,C and D (e.g its color).

B,C and D does not know anything about E yet, discarding the activity and blowing up their ActivitySequencer for E, because when
E sends another activity (now B,C and D may know E), the sequencer is still waiting for the former activity which was discarded. The sequencer stalls
for E unless a timeout occured AND E sends another activity.

Reported by: kargor

Original Ticket: dpp/bugs/758

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aspect: Consistency Issue with Saros' consistency handling
Projects
None yet
Development

No branches or pull requests

2 participants