Chorus Hub should not fail if multiple instances are running
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
This is a report on behalf of Peter Wulfing...
Currently, if multiple instances of Chorus Hub are running, it does not work. Also, it is difficult to determine that more than one instance is running without examining each person's computer.
Possible fixes:
- Chorus Hub should notify the user that multiple instances are running and allow him/her to choose which one they want to use.
- John Hatton proposed a less-expensive fix: All Chorus Hub instances should detect each other and put up a message saying that you have to turn off all but one.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating Chorus Hub startup and instance-management code, then reproduce the failure with multiple instances running. Done should mean multiple instances are detected and the user receives a clear message or can choose which instance to use, as decided by the maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100