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

List of repos / organizations does not refresh regularly #6

Closed
warthurton opened this Issue Jul 21, 2015 · 14 comments

Comments

Projects
None yet
8 participants
@warthurton

If you fork a report on github after you've already logged into the VS Plugin, when you try to clone the new repo it doesn't show up in the list. Doing some additional testing (deleting a repo, removing an organization) show that those aren't update either.

I believe the list of repos/organizations should refresh each time you open the clone repo window.

I would dig into the code, but the Community addition does not allow you to work on VS extensions.

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Jul 21, 2015

Collaborator

@warthurton Thanks for the report! The list of repos gets loaded from cache and periodically refreshed, but the refresh rate might be a bit on the long side, which ends up looking like it never refreshes. I'll take a look.

VS community edition is what I use to develop, so you can definitely use it to build extensions 😄 With 2015, there are no more restrictions in what you can do in VS, it is the equivalent of Pro in previous VS versions.

Collaborator

shana commented Jul 21, 2015

@warthurton Thanks for the report! The list of repos gets loaded from cache and periodically refreshed, but the refresh rate might be a bit on the long side, which ends up looking like it never refreshes. I'll take a look.

VS community edition is what I use to develop, so you can definitely use it to build extensions 😄 With 2015, there are no more restrictions in what you can do in VS, it is the equivalent of Pro in previous VS versions.

@warthurton

This comment has been minimized.

Show comment
Hide comment
@warthurton

warthurton Jul 21, 2015

Thanks for the info on VS Community. I just assumed and you know what happens then...

Thanks for the info on VS Community. I just assumed and you know what happens then...

@Haacked Haacked added the bug label Jul 31, 2015

@shana shana added this to the 1.0.13 milestone Aug 21, 2015

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Aug 21, 2015

Collaborator

Another user report about this. I'm bumping the priority on it so it's next on the list of things to fix.

Collaborator

shana commented Aug 21, 2015

Another user report about this. I'm bumping the priority on it so it's next on the list of things to fix.

@AndrewSav

This comment has been minimized.

Show comment
Hide comment
@AndrewSav

AndrewSav Sep 21, 2015

If it helps at all that "another user reported", please have yet another report - mine =). Fixing efforts are much appreciated!

If it helps at all that "another user reported", please have yet another report - mine =). Fixing efforts are much appreciated!

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Sep 21, 2015

Collaborator

Working on it!

Collaborator

shana commented Sep 21, 2015

Working on it!

@tannert44

This comment has been minimized.

Show comment
Hide comment
@tannert44

tannert44 Oct 23, 2015

Is there a fix for this yet?

Is there a fix for this yet?

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Oct 23, 2015

Collaborator

@tannert44 Not yet, but working on it!

Collaborator

shana commented Oct 23, 2015

@tannert44 Not yet, but working on it!

@lendrick

This comment has been minimized.

Show comment
Hide comment
@lendrick

lendrick Oct 27, 2015

Is there a work-around for this? If not, how long do I need to wait for the cache to refresh?

Is there a work-around for this? If not, how long do I need to wait for the cache to refresh?

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Oct 27, 2015

Collaborator

@lendrick I've ran more tests and looks like the cache refresh is really broken for repositories 😢
I'm bumping the priority on this one, but in the meantime, you can kill the cache by shutting down VS, going to %APPDATA%\GitHubVisualStudio and deleting the *.cache.db file corresponding to your server (for github.com, api.github.com.cache.db).

Make sure VS is not running when you do this, the extension might not like it if you yank the cache out from under it while it's running.

Collaborator

shana commented Oct 27, 2015

@lendrick I've ran more tests and looks like the cache refresh is really broken for repositories 😢
I'm bumping the priority on this one, but in the meantime, you can kill the cache by shutting down VS, going to %APPDATA%\GitHubVisualStudio and deleting the *.cache.db file corresponding to your server (for github.com, api.github.com.cache.db).

Make sure VS is not running when you do this, the extension might not like it if you yank the cache out from under it while it's running.

@jonburney

This comment has been minimized.

Show comment
Hide comment
@jonburney

jonburney Nov 26, 2015

+1 for this, I had the same issue today. I deleted the api.github.com.cache.db file and relaunched VS and the Github plugin was no-longer working or even visible at all. I'm using VS enterprise 2015. I restarted VS with the devenv.exe /log param and it worked fine after that

+1 for this, I had the same issue today. I deleted the api.github.com.cache.db file and relaunched VS and the Github plugin was no-longer working or even visible at all. I'm using VS enterprise 2015. I restarted VS with the devenv.exe /log param and it worked fine after that

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Nov 26, 2015

Collaborator

@jonburney Could you send me the extension log file so I can see what happened? It's at %LocalAppData%\GitHubVisualStudio\extension.log. If you could send that to support@github.com with a link to this issue, that would be great.

Collaborator

shana commented Nov 26, 2015

@jonburney Could you send me the extension log file so I can see what happened? It's at %LocalAppData%\GitHubVisualStudio\extension.log. If you could send that to support@github.com with a link to this issue, that would be great.

@jonburney

This comment has been minimized.

Show comment
Hide comment
@jonburney

jonburney Nov 26, 2015

I've had a look and there's nothing useful in there. Just these two lines for today (with my username stripped).

2015-11-26 12:24:19.1012|INFO|thread: 1|RepositoryHost|Log in from cache for login '{USERNAME}' to host 'https://api.github.com/' SUCCEEDED
2015-11-26 12:31:38.0255|INFO|thread: 1|RepositoryHost|Log in from cache for login '{USERNAME}' to host 'https://api.github.com/' SUCCEEDED

I'll try to reproduce again and get more detailed log data for you

I've had a look and there's nothing useful in there. Just these two lines for today (with my username stripped).

2015-11-26 12:24:19.1012|INFO|thread: 1|RepositoryHost|Log in from cache for login '{USERNAME}' to host 'https://api.github.com/' SUCCEEDED
2015-11-26 12:31:38.0255|INFO|thread: 1|RepositoryHost|Log in from cache for login '{USERNAME}' to host 'https://api.github.com/' SUCCEEDED

I'll try to reproduce again and get more detailed log data for you

@antoops

This comment has been minimized.

Show comment
Hide comment
@antoops

antoops Dec 18, 2015

Hi Shana, is this bug fixed or planned to fix in future version?
I suggest, if the repos are not refreshing loading time, at least giving a refresh button will give a manual sync with github. Now I am going ahead with logout-login

antoops commented Dec 18, 2015

Hi Shana, is this bug fixed or planned to fix in future version?
I suggest, if the repos are not refreshing loading time, at least giving a refresh button will give a manual sync with github. Now I am going ahead with logout-login

@shana

This comment has been minimized.

Show comment
Hide comment
@shana

shana Dec 18, 2015

Collaborator

A fix for this issue will be included in release 1.0.16.1, which will be out before Monday.

The vsix package is already available at https://github.com/github/VisualStudio/releases/tag/v1.0.16.1. If you could install it and test and let me know how it goes, that would be great!

Collaborator

shana commented Dec 18, 2015

A fix for this issue will be included in release 1.0.16.1, which will be out before Monday.

The vsix package is already available at https://github.com/github/VisualStudio/releases/tag/v1.0.16.1. If you could install it and test and let me know how it goes, that would be great!

@shana shana referenced this issue Dec 18, 2015

Merged

Release 1.0.16.2 #171

@shana shana closed this Jan 18, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment