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

VSCodium 1.41.1: "Error: Method not implemented. at ZigCompilerProvider.provideCodeActions" #29

Closed
metaleap opened this issue Jan 13, 2020 · 2 comments

Comments

@metaleap
Copy link

Just by navigating the cursor around in a .zig file, also on edits or saves or undos, I get such stacktraces:

[2020-01-13 19:30:39.176] [exthost] [error] [tiehuis.zig] provider FAILED
[2020-01-13 19:30:39.176] [exthost] [error] Error: Method not implemented.
	at ZigCompilerProvider.provideCodeActions (/home/_/.vscode/extensions/tiehuis.zig-0.2.3/out/zigCompilerProvider.js:20:15)
	at /home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:576:562
	at /home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:52:287
	at new Promise (<anonymous>)
	at Object.t.asPromise (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:52:259)
	at P.provideCodeActions (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:576:533)
	at /home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:595:972
	at B._withAdapter (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:591:697)
	at B.$provideCodeActions (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:595:950)
	at p._doInvokeHandler (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:663:275)
	at p._invokeHandler (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:662:971)
	at p._receiveRequest (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:661:588)
	at p._receiveOneMessage (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:660:468)
	at /home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:658:691
	at l.fire (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:893)
	at _.fire (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:189:274)
	at /home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:820:285
	at l.fire (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:893)
	at _.fire (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:189:274)
	at t.PersistentProtocol._receiveMessage (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:193:629)
	at /home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:190:824
	at l.fire (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46:893)
	at p.acceptChunk (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:186:737)
	at /home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:186:89
	at Socket.t (/home/_/a/vscodium/resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:195:68)
	at Socket.emit (events.js:200:13)
	at addChunk (_stream_readable.js:294:12)
	at readableAddChunk (_stream_readable.js:275:11)
	at Socket.Readable.push (_stream_readable.js:210:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:166:17)

Is it because it's WIP? Too new VSCode version? OS is Linux.

@metaleap
Copy link
Author

Ah dang silly me, now on further digging I see it's hardcoded in your source so likely just a WIP artifact. Well can keep it open until the issue does go away :D

@tiehuis
Copy link
Member

tiehuis commented Feb 21, 2020

I just removed this stub for the moment which should have stopped this error message printing. However I was unable to reproduce it exactly with my setup so let me know if this happens to have not helped.

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

2 participants