microsoft / microsoft/VFSForGit
Clone always picks default cache server
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 474
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 8
Description
Instead of always picking the default cache server for the account, it should look through the cache servers available for the repository and pick the one that has the best apparent connectivity.
It may be a good idea to occasionally reconsider the cache server location - say at gvfs-mount time - to account for changes in the cache server list or the client's location.
Contributor guide
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
Start by locating the clone path that selects the account's default cache server and the code exposing cache servers available for a repository. Investigate how apparent connectivity and gvfs-mount-time reconsideration should be defined; done means selecting the best available server and handling location or server-list changes, with tests covering the selection behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100