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.

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

GitLens can't see the remote but git can #649

Closed
gbritton1 opened this issue Feb 7, 2019 · 18 comments

Comments

@gbritton1
Copy link

commented Feb 7, 2019

image

@eamodio

This comment has been minimized.

Copy link
Owner

commented Feb 18, 2019

What command are you executing to get that error? It looks like the error is coming from vscode itself (as GitLens uses some vscode commands for push/pull/fetch).

@gbritton1

This comment has been minimized.

Copy link
Author

commented Feb 18, 2019

Just wanted to do a pull

@gbritton1

This comment has been minimized.

Copy link
Author

commented Feb 18, 2019

Right click, pull

@eamodio

This comment has been minimized.

Copy link
Owner

commented Feb 18, 2019

Hrm -- can you do a pull from the vscode Source Control side bar (under the ... menu) or via the command palette?

@gbritton1

This comment has been minimized.

Copy link
Author

commented Feb 19, 2019

@eamodio

This comment has been minimized.

Copy link
Owner

commented Jul 9, 2019

@gbritton1 is this still an issue?

@gbritton1

This comment has been minimized.

Copy link
Author

commented Jul 9, 2019

@BMBurstein

This comment has been minimized.

Copy link

commented Jul 30, 2019

I am having a similar issue. gitlens only sees one of my 2 remotes:

image

@eamodio

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

Can you please enable output channel logging by setting "gitlens.outputLevel": "debug" in your settings.json. This will enable logging to the GitLens channel in the Output pane. Once enabled, please reproduce the issue (if possible) and attach the log lines from the GitLens channel.

@BMBurstein

This comment has been minimized.

Copy link

commented Jul 30, 2019

From the GitLens channel:

[2019-07-30 19:39:59:258] [11c] RepositoriesView.refreshNode — e=RemotesNode(gitlens:repository(/homes/user/work/B0004.00.4030):remotes), t=true
[2019-07-30 19:39:59:258] [11d] RepositoriesView.triggerNodeChange — e=RemotesNode(gitlens:repository(/homes/user/work/B0004.00.4030):remotes)
[2019-07-30 19:39:59:258] [11d] RepositoriesView.triggerNodeChange completed • 0 ms
[2019-07-30 19:39:59:258] [11c] RepositoriesView.refreshNode completed • 0 ms
[2019-07-30 19:39:59:573] [/homes/user/work/B0004.00.4030] git remote -v • 109 ms 
[2019-07-30 19:39:59:574] [11e] GitRemoteParser.parse completed • 0 ms

From the GitLens (git) channel:

[2019-07-30 19:39:59:573] [/homes/user/work/B0004.00.4030] git remote -v • 109 ms 
@eamodio

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

@BMBurstein Thanks -- can you send me the output of git remote -v ?

@BMBurstein

This comment has been minimized.

Copy link

commented Jul 30, 2019

As much as I can share of it is in the image I posted. Here is a sample output. It is the same format as my real output.:

> git remote -v
origin  /home/user1/repos/B0004.02.4033 (fetch)
origin  /home/user1/repos/B0004.02.4033 (push)
radion  /home/user2/repos/B0004.02.4033/ (fetch)
radion  /home/user2/repos/B0004.02.4033/ (push)

As I am pasting and editing the above output I noticed that the remote that gitlens is ignoring has a trailing slash. I hadn't noticed that before. Relevant?

@eamodio

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

Thanks! I see the issue and will be fixed in the next release.

@eamodio eamodio self-assigned this Jul 30, 2019

@eamodio eamodio added this to the Soon™ milestone Jul 30, 2019

@eamodio eamodio changed the title GitLens can't see the remote but git can? GitLens can't see the remote but git can Jul 30, 2019

@eamodio

This comment has been minimized.

Copy link
Owner

commented Jul 30, 2019

@gbritton1 I've moved your issue here: #807 (sorry about the confusion)

@BMBurstein

This comment has been minimized.

Copy link

commented Jul 31, 2019

Thank you for the quick fix.
I'm sorry for hijacking the original thread. I thought the two were related.

@BMBurstein

This comment has been minimized.

Copy link

commented Jul 31, 2019

I just found that in a different repo it is the other way round. The first remote listed in git remote -v has the trailing slash, and GitLens only lists that one. Is this the same issue? Does this fix fix this too?

@gbritton1

This comment has been minimized.

Copy link
Author

commented Jul 31, 2019

Problem resolved for me with latest version

@eamodio

This comment has been minimized.

Copy link
Owner

commented Jul 31, 2019

@BMBurstein it should fix it either way. It really wasn't about the slash, but instead that the remote wasn't a http[s]/git/ssh url

@eamodio eamodio closed this in d5f8abe Aug 1, 2019

@eamodio eamodio removed this from the Soon™ milestone Aug 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.