Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

error trying to perform any command #24

Closed
rspaulino opened this issue Jul 9, 2016 · 5 comments
Closed

error trying to perform any command #24

rspaulino opened this issue Jul 9, 2016 · 5 comments
Labels

Comments

@rspaulino
Copy link

running latest version of macOS
running latest version of vscode
running git-creditial-manager

I have install and configure the vsts extension for visual studio code but every time I try to perform any command I get a 404 error. The url don't seen to match I don't know if this is part of the problem or they are just different because this are API call

vscode error: (team) Failed Request: Not Found(404) - https://****consulting.visualstudio.com/****Consulting/_apis/git

vsts working url: https://*****consulting.visualstudio.com/_git/aspnetcore

screen shot 2016-07-09 at 12 57 55 am

screen shot 2016-07-09 at 1 01 01 am

@jeffyoung
Copy link
Contributor

Thanks for reporting. It appears the URLs to the REST endpoints are getting set incorrectly. Could I ask you to turn on the logging, repro the issue and send the log file to me at jeyou at microsoft dot com? I'd like to take a look and see what's going wrong.

Also, is the URL segment after ".visualstudio.com/" the same as the name of your account? That is, is "**consulting" and "**Consulting" the same value?

Thanks!

@rspaulino
Copy link
Author

@jeffyoung thank, I have sent you the log, let me know if you got it.

Yes but that is the one where I get the 404 error.

@jeffyoung
Copy link
Contributor

Thanks! I've taken a look at the log and sent you a private fix which I hope will get you around the issue. I'll need to test it a bit more but submitting it.

@jeffyoung
Copy link
Contributor

Thanks for verifying the fix. I'll get more testing done and get a PR some time soon.

@jeffyoung jeffyoung added the bug label Jul 25, 2016
jeffyoung pushed a commit that referenced this issue Jul 29, 2016
* Fix 'collection in the domain' issue (#24, #25 )

* Add test for case insensitivity

Add test for case insensitivity for the 'collection in the domain' scenario (where the collection and account name are the same but differ only in case).
@jeffyoung
Copy link
Contributor

Should now be fixed in release 104.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants