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

Running the contributed command: 'reason-language-server.restart' failed. #433

Open
lesha1201 opened this issue Mar 28, 2020 · 0 comments
Open

Comments

@lesha1201
Copy link

I have a problem when trying to restart reason language server. When it's active and I run the command reason-language-server.restart it fails but when I run it again it successfully starts the language server.

In Log (Extension Host) I have the following error when it fails:
image

[2020-03-28 10:17:01.828] [exthost] [error] Error: EBUSY: resource busy or locked, open 'c:\Users\lesha\.vscode\extensions\jaredly.reason-vscode-1.7.8\bin.native.exe.hot.exe'
	at Object.openSync (fs.js:447:3)
	at Object.func (electron/js2c/asar.js:140:31)
	at Object.func [as openSync] (electron/js2c/asar.js:140:31)
	at Object.writeFileSync (fs.js:1206:35)
	at restart (c:\Users\lesha\.vscode\extensions\jaredly.reason-vscode-1.7.8\src\index.js:144:16)
	at _executeContributedCommand (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:549:220)
	at _.$executeContributedCommand (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:549:595)
	at p._doInvokeHandler (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:688:464)
	at p._invokeHandler (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:688:156)
	at p._receiveRequest (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:686:817)
	at p._receiveOneMessage (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:685:623)
	at c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:683:791
	at l.fire (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:48:845)
	at v.fire (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:191:325)
	at c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:851:104
	at l.fire (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:48:845)
	at v.fire (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:191:325)
	at t.PersistentProtocol._receiveMessage (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:195:717)
	at c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:192:897
	at l.fire (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:48:845)
	at p.acceptChunk (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:188:897)
	at c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:188:249
	at Socket.t (c:\Users\lesha\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:197:232)
	at Socket.emit (events.js:203:13)
	at addChunk (_stream_readable.js:295:12)
	at readableAddChunk (_stream_readable.js:276:11)
	at Socket.Readable.push (_stream_readable.js:210:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:166:17) reason-language-server.restart

I'm not sure if it's something happens only on my PC or it's a general issue on Windows.

System information:

  • OS: Windows 10 1909
  • node: v12.7.0
  • npm: v6.10.0
  • bsb: v7.2.2
  • VSCode: v1.43.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant