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

Extension - File Utils - 'Duplicate' command fails #3127

Open
bryphe opened this issue Feb 10, 2021 · 0 comments
Open

Extension - File Utils - 'Duplicate' command fails #3127

bryphe opened this issue Feb 10, 2021 · 0 comments
Labels
A-extension Area: Extension/plugin integration, vscode or VimL bug Something isn't working

Comments

@bryphe
Copy link
Member

bryphe commented Feb 10, 2021

Pulling out from #1058 (thanks @mabasic!)

The Duplicate command in the file-utils extension fails. Looking at the log, I see this failure:

[ERROR] [ 4.018s] Oni2.Extension.ClientStore : {"$isError":true,"name":"Error","message":"Contributed command 'fileutils.duplicateFile' does not exist.","stack":"Error: Contributed command 'fileutils.duplicateFile' does not exist.\n\tat ExtHostCommands.$executeContributedCommand (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/workbench/api/common/extHostCommands.js:174:39)\n\tat RPCProtocol._doInvokeHandler (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/workbench/services/extensions/common/rpcProtocol.js:341:27)\n\tat RPCProtocol._invokeHandler (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/workbench/services/extensions/common/rpcProtocol.js:326:45)\n\tat RPCProtocol._receiveRequest (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/workbench/services/extensions/common/rpcProtocol.js:253:32)\n\tat RPCProtocol._receiveOneMessage (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/workbench/services/extensions/common/rpcProtocol.js:181:26)\n\tat /tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/workbench/services/extensions/common/rpcProtocol.js:65:52\n\tat Emitter.fire (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/common/event.js:479:38)\n\tat BufferedEmitter.fire (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/parts/ipc/common/ipc.net.js:375:35)\n\tat /tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/workbench/services/extensions/node/extensionHostProcessSetup.js:146:41\n\tat Emitter.fire (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/common/event.js:479:38)\n\tat BufferedEmitter.fire (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/parts/ipc/common/ipc.net.js:375:35)\n\tat PersistentProtocol._receiveMessage (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/parts/ipc/common/ipc.net.js:654:41)\n\tat /tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/parts/ipc/common/ipc.net.js:510:83\n\tat Emitter.fire (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/common/event.js:479:38)\n\tat ProtocolReader.acceptChunk (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/parts/ipc/common/ipc.net.js:189:37)\n\tat /tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/parts/ipc/common/ipc.net.js:158:61\n\tat Socket.listener (/tmp/.mount_Onivim4hx97Y/usr/share/node/node_modules/@onivim/vscode-exthost/out/vs/base/parts/ipc/node/ipc.net.js:17:40)\n\tat Socket.emit (events.js:315:20)\n\tat addChunk (_stream_readable.js:295:12)\n\tat readableAddChunk (_stream_readable.js:271:9)\n\tat Socket.Readable.push (_stream_readable.js:212:10)\n\tat Pipe.onStreamRead (internal/stream_base_commons.js:186:23)"}

Need to investigate and see how that command is being contributed (or, see if there was an activation error on the extension preventing it from being registered).

@bryphe bryphe added bug Something isn't working A-extension Area: Extension/plugin integration, vscode or VimL labels Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-extension Area: Extension/plugin integration, vscode or VimL bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant