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

"RLS Starting" with vscode's workspaces #588

Closed
not-fl3 opened this issue May 15, 2019 · 3 comments
Closed

"RLS Starting" with vscode's workspaces #588

not-fl3 opened this issue May 15, 2019 · 3 comments

Comments

@not-fl3
Copy link

not-fl3 commented May 15, 2019

Hello!

With the following project configuration the rls is working fine in on of the crates("foo" or "bar", depending on which one was opened first), but "RLS Starting" hangs forever in the second one. Is it a known bug?

mkdir workspaces_test && cd workspaces_test
cat <<EOF > test.code-workspace
{
	"folders": [
		{
			"path": "bar"
		},
		{
			"path": "foo"
		}
	],
	"settings": {}
}
EOF
cargo init --bin foo
cargo init --bin bar
code test.code-workspace

Tested on rls 1.34.0 (0d6f53e 2019-02-14) and rls 1.36.0 (5b8e99b 2019-05-01)

@not-fl3 not-fl3 changed the title "RLS Starging" with vscode's workspaces "RLS Starting" with vscode's workspaces May 15, 2019
@zkat
Copy link
Contributor

zkat commented May 27, 2019

I managed to figure out how to debug extensions aaaand... it turns out this looks like it's being caused by ClientWorkspace#registerCommands() being executed again. My current VS Code version doesn't allow registering multiple commands. I'm working on a patch to fix this right now, and I'll update if I end up dropping the task. Below is the stack trace:

rejected promise not handled within 1 second: Error: command 'rls.update' already exists
stack trace: Error: command 'rls.update' already exists
	at d.registerCommand (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:496:447)
	at Object.registerCommand (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:715:422)
	at ClientWorkspace.registerCommands (/Users/zkat/Documents/code/personal/rust/rls-vscode/out/extension.js:221:58)
	at ClientWorkspace.<anonymous> (/Users/zkat/Documents/code/personal/rust/rls-vscode/out/extension.js:203:18)
	at Generator.next (<anonymous>)
	at __awaiter (/Users/zkat/Documents/code/personal/rust/rls-vscode/out/extension.js:7:71)
	at new Promise (<anonymous>)
	at __awaiter (/Users/zkat/Documents/code/personal/rust/rls-vscode/out/extension.js:3:12)
	at ClientWorkspace.start (/Users/zkat/Documents/code/personal/rust/rls-vscode/out/extension.js:161:16)
	at didOpenTextDocument (/Users/zkat/Documents/code/personal/rust/rls-vscode/out/extension.js:61:19)
	at vscode_1.workspace.onDidOpenTextDocument.doc (/Users/zkat/Documents/code/personal/rust/rls-vscode/out/extension.js:26:57)

zkat added a commit to zkat/rls-vscode that referenced this issue May 29, 2019
@zkat
Copy link
Contributor

zkat commented May 29, 2019

@not-fl3 I still have to do some work and refactoring on it before it's 100% there, but if you want to get this bit working in the process, you can just clone zkat@6e5cae8 and run npm i && npm run installDevExtension.

zkat added a commit to zkat/rls-vscode that referenced this issue Jun 12, 2019
@zkat
Copy link
Contributor

zkat commented Jun 12, 2019

#601 is a thing now. Cheers.

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

Successfully merging a pull request may close this issue.

2 participants