Cannot Update/Bootstrap `rust-analyzer` in Visual Studio Code

[HTGAzureX1212]

Updating the rust-analyzer nightly distribution currently does not work in the Visual Studio Code Rust Analyzer Extension.

From the OUTPUT tab:

ERROR [15/06/2021, 15:42:43]: Bootstrap error [TypeError: Only absolute URLs are supported
	at getNodeRequestOptions (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:20682:9)
	at c:\Users\harry\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:20787:19
	at new Promise (<anonymous>)
	at Object.fetch (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:20784:9)
	at c:\Users\harry\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:22713:36
	at downloadFile (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:22714:7)
	at c:\Users\harry\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:22693:15
	at C._withProgress (<path redacted>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:84:44110)
	at C.withProgress (<path redacted>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:84:43864)
	at Object.withProgress (<path redacted>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:93:30045)
	at Object.download (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:22687:45)
	at <path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:23057:19
	at downloadWithRetryDialog (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:23095:26)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)
	at async getServer (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:23056:5)
	at async bootstrapServer (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:22957:18)
	at async bootstrap (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:22893:18)
	at async tryActivate (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:22778:24)
	at async activate (<path redacted>\.vscode\extensions\matklad.rust-analyzer-0.3.638\out\src\main.js:22769:5)]

[lnicola]

Duplicate of #9280.

[HTGAzureX1212]

I updated the extension and now I am getting this error: Bootstrap error [Error: ENOENT: no such file or directory, open 'C:\C:\Users\<user>\AppData\Roaming\Code\User\globalStorage\matklad.rust-analyzer\rust-analyzer-x86_64-pc-windows-msvc6e0f2e9b82'] 🤔

[lnicola]

6e0f2e9b82 huh?

CC @wxb1ank ^.

[SomeoneToIgnore]

In my case, the error is a bit different (macOs), but some similarity with the hash-on-the-end is definitely there:

[simbiont666]

Have the same @SomeoneToIgnore

[lnicola]

In my case, the error is a bit different (macOs)

That sounds like it's already running?

[simbiont666]

rm rust-analyzer-x86_64-apple-darwin*
in ../matklad.rust-analyzer directory and Retry download solved the problem for now..

[SomeoneToIgnore]

That sounds like it's already running?

I don't think so, at least custom r-a commands are not registered in VSCode by that time, I also don't see any rust-analyzer status in the VSCode footer:

Nothing in the ps output too.

I only start r-a when it happens.
First, it notices the client update and downloads it (the very first start, no updates on consequent restarts ofc) and then tries to download (that works) and update the server binary (that fails).

Before the recent client changes, it was able to do so and start the server, but not now.

[RagibHasin]

I updated the extension and now I am getting this error: Bootstrap error [Error: ENOENT: no such file or directory, open 'C:\C:\Users\<user>\AppData\Roaming\Code\User\globalStorage\matklad.rust-analyzer\rust-analyzer-x86_64-pc-windows-msvc6e0f2e9b82'] 🤔

same here

[wxb1ank]

This is a bit unexpected. It looks a lot like #8956, but the purpose of #8951 was fixing that. My recent client PR, #9281, doesn't touch this either. I'm tired and need to sleep; I'll look at this later in the morning.

[wxb1ank]

Ah, I think I've got it, actually. Looks like another regression from #8956 :/. Uri.path is used in many places where Uri.fsPath should be. (Why is vscode.Uri so confusing?) I need to test to confirm such a Ctrl+R job would resolve this particular error.

I'll draft a PR for this issue along with another bugfix in #8956.

[Xunjin]

A manual fix which worked for me was deleted all targets in noted folder and restart VSCode, hope it helps until we have a solution.

PS: it's a dirty workaround, sorry :/