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

Try to address duplicate open group message issues after sleep #915

Merged
merged 1 commit into from Feb 25, 2020

Conversation

neuroscr
Copy link

Try to address #866, untested but wanted to make the PR easily mergeable as not to miss the next release

@Mikunj
Copy link

Mikunj commented Feb 24, 2020

This looks like it might work. If it doesn't then i would look to see if multiple message receivers are instantiated somehow.

@neuroscr
Copy link
Author

neuroscr commented Feb 24, 2020

Yea that’s also possible; I’ve instrumented one of my dev copies with additional logging to track this already but having stability problems with my hardware still.

Also these current events also prove that if multiple message receivers are instantiated somehow, they shouldn't be, we only need this emit handler in one of them (which this PR handles exactly)

Copy link

@Mikunj Mikunj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's get this merged if you think it's good

@neuroscr neuroscr merged commit 20c7a42 into oxen-io:clearnet Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants