-
Notifications
You must be signed in to change notification settings - Fork 13
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
[BUG] <Cannot work with project source controlled by "Perforce for VS Code" extension> #1475
Comments
Going by the stack, could this be related to either dotnet/vscode-csharp#7514 or dotnet/vscode-csharp#7399 @dibarbet ? |
I'm seeing the same issue, glad I found this. Currently sitting with debugger attached to the language server, the string that is failing to parse as a URI for me is Not sure why that Edit: "in there" -> "in the hostname of the uri string" |
See dotnet/vscode-csharp#6256 (comment) Some of the the perforce URIs I believe are invalid - the host should not be pct encoded. On other ones, the URI is fine, but At least the incorrect URIs (with invalid host names) should be updated by the perforce extension. We use |
I'll reach out to the vscode-perforce repo to figure out why they're putting the revision as the authority component. https://github.com/mjcrouch/vscode-perforce/blob/7bd13fd4e650fc98e86bf147d4e09968bbeaf6a9/src/PerforceUri.ts#L69 Do you know if the authority component has special significance for the language server or is the whole uri simply used as an identifier for the text document? Sorry if moot/lost question, I'm not deep into this. :-) |
Ah, here's a related issue in the extension repo. ✨ |
Apologies for the late reply - the authority isn't particularly important - just needs to be parseable by |
transferred over to the C# extension side for tracking - dotnet/vscode-csharp#7638 |
Describe the Issue
When enable the extention plugin "Perforce for VS Code", the total function will not work and it says:
Steps To Reproduce
Expected Behavior
No response
Environment Information
Windows, C# Dev Kit v1.10.18, Perforce for VS Code v4.15.7
The text was updated successfully, but these errors were encountered: