search

Sertion / vscode-gitblame

Visual Studio Code Extension - See Git Blame info in status bar.
https://marketplace.visualstudio.com/items/waderyan.gitblame
MIT License
72 stars 31 forks source link

Stuck Waiting for git blame response (6.0.0) #95

Closed pftbest closed 3 years ago

pftbest commented 3 years ago

The last lines in the log are:

[ 16:31:09 | command ] git symbolic-ref -q --short HEAD
[ 16:31:09 | command ] git ls-remote --get-url origin
[ 16:31:09 | command ] git config branch.prod.remote
[ 16:31:09 | command ] git ls-files --full-name xxx.c
[ 16:31:09 | command ] git config remote.origin.url

However my repo is created with git-svn so it doesn't have any remotes. I guess thats why this extension fails because it cant find a remote.

Sertion commented 3 years ago

Hey Vadzim!

Looks like a rare use-case that I have missed to take into consideration. Will look into a fix as soon as I am able.

Sertion commented 3 years ago

I've posted an update to the marketplace. Please report back if it did not solve the issue.

pftbest commented 3 years ago

Hello,

Thank you for looking at this! Unfortunately the version 6.0.1 does not help in my case, it still behaves the same way as the old version and gets stuck.

To help you diagnose the issue I have found a very small public svn repo which you can clone to reproduce the problem. Please try

sudo apt install git-svn

git svn clone https://svn.code.sf.net/p/log4j-advanced/code/trunk

Then open trunk directory in vscode and try to use git blame plugin.

Sertion commented 3 years ago

I misunderstood what the issue was. The repository was very helpful. I think I have solved it now. The new version is processing right now. It should be live any moment.

pftbest commented 3 years ago

Now it works fine, thank you!