-
Notifications
You must be signed in to change notification settings - Fork 582
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
Wrong remote protocol #1488
Comments
By chance were you working from a fork of the original repository where the PR was submitted? I got the same error as you as follows (specifics left in for reproducibility):
Log (with error):[Info] Looking for git repository [Info] Git repository found, initializing review manager and pr tree view. [Info] Review> Validate state in progress [Info] Review> Validating state... [Info] No remote with name 'upstream' found. [Info] Found GitHub remote [Info] Review> no matching pull request metadata found for current branch master [Info] Review> Queuing additional validate state [Info] Review> no matching pull request metadata found on GitHub for current branch master [Info] Review> Validating state... [Info] Found GitHub remote [Info] Review> no matching pull request metadata found for current branch master [Info] Review> no matching pull request metadata found on GitHub for current branch master [Info] Review> switch to Pull Request #15 - start [Info] PullRequestGitHelper> Branch pr/kirafanautodec/15 is from a fork. Create a remote first. [Info] PullRequestGitHelper> create remote for https://github.com/kirafanautodec/decrunch. [Info] Review> checkout failed #{"message":"Failed to execute git","stdout":"","stderr":"fatal: unable to look up git@github.com:kirafanautodec (port 9418) (nodename nor servname provided, or not known)\n","exitCode":128,"gitCommand":"fetch","gitArgs":["fetch","kirafanautodec","master:pr/kirafanautodec/15","--depth=1"]} [Info] Review> Queuing additional validate state [Info] Review> Validating state... [Info] Found GitHub remote [Info] Review> no matching pull request metadata found for current branch master [Info] Review> no matching pull request metadata found on GitHub for current branch master However, everything worked as expected when I cloned the original (where the PR was actually submitted):
Log (with success):[Info] Looking for git repository [Info] Git repository found, initializing review manager and pr tree view. [Info] Review> Validate state in progress [Info] Review> Validating state... [Info] No remote with name 'upstream' found. [Info] Found GitHub remote [Info] Review> no matching pull request metadata found for current branch master [Info] Review> no matching pull request metadata found on GitHub for current branch master [Info] Review> switch to Pull Request #15 - start [Info] PullRequestGitHelper> Branch pr/kirafanautodec/15 is from a fork. Create a remote first. [Info] PullRequestGitHelper> create remote for https://github.com/kirafanautodec/decrunch. [Info] PullRequestGitHelper> associate pr/kirafanautodec/15 with Pull Request #15 [Info] Review> Review> switch to Pull Request #15 - done [Info] Review> Queuing additional validate state [Info] Review> Validating state... [Info] No remote with name 'upstream' found. [Info] Found GitHub remote [Info] Review> current branch pr/kirafanautodec/15 is associated with pull request #15 [Info] Review> Resolving pull request [Info] Review> Fetching pull request data [Info] Review> register comments provider [Info] Review> display pull request status bar indicator and refresh pull request tree view. I suppose it can be argued whether PRs for the original repo should be shown in the forked repo by the extension, as they're not shown that way on GitHub itself. The bug in this case might be resolved by not displaying them at all, but if it's decided they should be displayed then they should probably be just as "checkout-able" as others. |
I tried this out, and I wasn't able to reproduce the issue. If you're still seeing it please ping this issue or open a new one and I will investigate further! |
It's been a while without hitting this issue. I guess some commit made a fix. |
Steps to Reproduce:
origin git@github.com:Glandos/project.git
author git://git@github.com:author/project
The text was updated successfully, but these errors were encountered: