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

HLAPI Syncgroup Double Join on invite #1413

Open
afandria opened this issue Jul 22, 2016 · 1 comment
Open

HLAPI Syncgroup Double Join on invite #1413

afandria opened this issue Jul 22, 2016 · 1 comment
Assignees
Labels

Comments

@afandria
Copy link

It appears (at least on TODOs) that we might be double joining a syncgroup. These back-to-back joins are triggering an error in the code, but we shouldn't be firing the invite callback twice in the first place.

Is it possible that we're advertising double?

@azinman

@afandria afandria added the Bug label Jul 22, 2016
@afandria afandria added this to the Syncbase HLAPI Complete milestone Jul 22, 2016
@afandria afandria self-assigned this Jul 22, 2016
@afandria
Copy link
Author

No, this isn't actually a double advertise. It's actually "normal".

We join once from syncgroup invite and once from userdata watch. This error started being logged because the lower layer had a bug introduced into it. We are looking into fixing it in v.io/c/23930

The error is that a collection (from the syncgroup) does not exist. This error tends to fire after a double join; the second join notices that the collection doesn't yet exist, but fails to realize that the sync is still pending (so it's okay for the collection not to exist yet).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant