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

Automatic connect doesn't work correctly if there are multiple thorium servers #6

Closed
TimPietrusky opened this issue Jul 10, 2019 · 0 comments
Closed

Automatic connect doesn't work correctly if there are multiple thorium servers #6

TimPietrusky opened this issue Jul 10, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@TimPietrusky
Copy link
Member

Issue description

When using the automatic-connect feature to find thorium servers in the network, luminave-thorium connects to new servers that are found, even when there is already an established connection.

Steps to reproduce

  • Start luminave-thorium
  • Start Thorium 1
  • See that luminave-thorium connects to Thorium 1
  • Start Thorium 2
  • See that luminave-thorium connects to Thorium 2

Versions

  1. luminave-thorium: 1.2.3
@TimPietrusky TimPietrusky added the bug Something isn't working label Jul 10, 2019
TimPietrusky pushed a commit that referenced this issue Jul 18, 2019
@semantic-release-bot
chore(release): 1.2.4 [skip ci]
a0adbb0 
## [1.2.4](v1.2.3...v1.2.4) (2019-07-18)

### Bug Fixes

* **bonjour:** Find just one thorium server ([54e14df](54e14df)), closes [#6](#6)
@TimPietrusky TimPietrusky mentioned this issue Jul 21, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TimPietrusky