Cloning the Repo in VS 19 and 22

Open
#128 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
git
Domain
developer-experience, tooling

Research direction

Start by reproducing the clone and checkout failure from Visual Studio 19 or 22 on Windows 10 or 11, using the environment details in the issue. No files or tests are identified; done means the repository clones, checks out successfully, and loads into a solution without the reported error.

Written by the indexing model from the issue text.

Description

Issue-Bug
Brief description of your issue

when Cloning the repo "Git failed with fatal error. the remote end hung unexpectedly" Clone succeeded, but checkout failed. the remote end hung up unexpectedly

Steps to reproduce

Use clone from Repo on VS 19 or VS 22

Expected behavior

The repo is to be cloned and loaded into a solution within Visual Studio.

Actual behavior

No solution, error message shows when Cloning the repo "Git failed with fatal error. the remote end hung unexpectedly" Clone succeeded, but checkout failed. the remote end hung up unexpectedly

Environment
Windows 10 10.0.19043 build 19043 
Windows 11 10.0.22000 build 22000

Visual studio v19 & V22 (tested with)
Dominant language
C#
Stars
317
Forks
79
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/winget-cli-restsource

All issues in microsoft/winget-cli-restsource

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.