Skip to content
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

Workspace folders from different providers #94191

Closed
dbaeumer opened this issue Apr 1, 2020 · 6 comments
Closed

Workspace folders from different providers #94191

dbaeumer opened this issue Apr 1, 2020 · 6 comments
Assignees
Labels
debt Code quality issues workbench-multiroot Multi-root (multiple folders) issues
Milestone

Comments

@dbaeumer
Copy link
Member

dbaeumer commented Apr 1, 2020

When I use LSIF together with WSL I always get this message:

capture

Why do we have this limitation? I don't see this under Windows since there I have a normal file provider.

@bpasero bpasero assigned isidorn and unassigned bpasero Apr 2, 2020
@bpasero
Copy link
Member

bpasero commented Apr 2, 2020

From 0e6822b

@bpasero bpasero added the workbench-multiroot Multi-root (multiple folders) issues label Apr 2, 2020
@dbaeumer
Copy link
Member Author

dbaeumer commented Apr 2, 2020

@isidorn can you explain the underlying reason for this.

@isidorn
Copy link
Contributor

isidorn commented Apr 2, 2020

@dbaeumer we do not allow workspace folders with different schemas. We always had this limitation - the exact reason I forgot to be honest.
Here are some issues with more details
https://github.com/microsoft/vscode-remote/issues/1608
#75273
Also @aeschli might know more since I remember him being the original person that I discussed this with.

@isidorn isidorn added the under-discussion Issue is under discussion for relevance, priority, approach label Apr 2, 2020
@aeschli
Copy link
Contributor

aeschli commented Apr 3, 2020

@isidorn We want to prevent that local folders are added to remote workspaces. Your check prevents too much.
Can you change the check to

if (this.environmentService.configuration.remoteAuthority) {
   foldersToAdd = foldersToAdd.filter(f => f.uri.scheme !== Schemas.file);
}

also remote folders from different remotes should be disallowed:

const remoteAuthority = this.environmentService.configuration.remoteAuthority;
if (remoteAuthority) {
   foldersToAdd = foldersToAdd.filter(f => f.uri.scheme !== Schemas.file && (f.uri.scheme !== Schemas.vscodeRemote || hasEqualAuthority(f.uri.authority, remoteAuthority)));
}

@isidorn
Copy link
Contributor

isidorn commented Apr 3, 2020

@aeschli thanks for refershing my memory.
Yes, we can loosen the check. Let's do that start of next week.

@isidorn isidorn added debt Code quality issues and removed under-discussion Issue is under discussion for relevance, priority, approach labels Apr 3, 2020
@isidorn isidorn added this to the April 2020 milestone Apr 3, 2020
@dbaeumer
Copy link
Member Author

dbaeumer commented Apr 3, 2020

@isidorn & @aeschli Thanks. Will make my LSIF live easier.

@isidorn isidorn closed this as completed in deb33e0 Apr 6, 2020
@github-actions github-actions bot locked and limited conversation to collaborators May 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debt Code quality issues workbench-multiroot Multi-root (multiple folders) issues
Projects
None yet
Development

No branches or pull requests

4 participants