You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Open Visual studio on 2 different VM's, not logged in on either
VM 1, login
VM 2, login
VM 1, create new local repository
VM 1, publish newly created repository (produces bad credentials error)
VM 1, publish a repository via manage connections -> github -> create (notice the dialog freezes)
Expected result: Each instance is treated individually without an issue to publishing and syncing.
Actual result: After signing in on a separate VM, bad credentials error message.
Extension.log
2016-05-03 12:38:57.0333|ERROR|thread:12|RepositoryPublishViewModel|Octokit.AuthorizationException: Bad credentials
at Octokit.Connection.HandleErrors(IResponse response) in Y:\jenkins\workspace\GitHub for Visual Studio speakeasy jenkinskeep\submodules\octokit.net\Octokit\Http\Connection.cs:line 563
at Octokit.Connection.<RunRequest>d__51.MoveNext() in Y:\jenkins\workspace\GitHub for Visual Studio speakeasy jenkinskeep\submodules\octokit.net\Octokit\Http\Connection.cs:line 545
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Octokit.Connection.<Run>d__50`1.MoveNext() in Y:\jenkins\workspace\GitHub for Visual Studio speakeasy jenkinskeep\submodules\octokit.net\Octokit\Http\Connection.cs:line 530
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Octokit.ApiConnection.<Post>d__17`1.MoveNext() in Y:\jenkins\workspace\GitHub for Visual Studio speakeasy jenkinskeep\submodules\octokit.net\Octokit\Http\ApiConnection.cs:line 0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Octokit.RepositoriesClient.<Create>d__3.MoveNext() in Y:\jenkins\workspace\GitHub for Visual Studio speakeasy jenkinskeep\submodules\octokit.net\Octokit\Clients\RepositoriesClient.cs:line 90
{"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
2016-05-03 12:39:11.7812|INFO|thread: 1|RepositoryHost|Logged off of host 'https://api.github.com/'
2016-05-03 12:39:11.7968|INFO|thread: 1|LoginCache|Erasing the git credential cache for host 'https://github.com/'
Steps to reproduce:
Expected result: Each instance is treated individually without an issue to publishing and syncing.
Actual result: After signing in on a separate VM, bad credentials error message.
Extension.log