Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [lsp4j-dev] Lsp4j Usage for TCL

Maybe there is an eclipse way ? How to test my lsp inside eclipse ?
Le dim. 19 août 2018 à 09:45, Guillaume Dufour <guillaume.duff@xxxxxxxxx> a écrit :
Hello,

I start to create a TCL LSP based on LSP 4J

Thanks for all your work.

I just want to know the best dev process.
I load my extension with vsix file.
I enable java remote debug on the extension file (with suspen yes). It seems working but a little pane, to reload every time and launch remote debug.

And in fact, i am facing a bug (probably a packaging problem), vscode reply have an error but no break point are reach on java side after server start listening (i put breakpoint on all  class and method of workspace service and document service and on all java exception).

I think i use a bad dev process, that's why i miss the problem ? or maybe a bad packaging.  my vscode is a 1.26 version, is it a problem ?

Have a nice day.

dufgui.vscode-tcl]Header must provide a Content-Length property.
e.$onExtensionRuntimeError @ mainThreadExtensionService.ts:43
e._doInvokeHandler @ rpcProtocol.ts:261
e._invokeHandler @ rpcProtocol.ts:246
e._receiveRequest @ rpcProtocol.ts:192
e._receiveOneMessage @ rpcProtocol.ts:174
(anonymous) @ rpcProtocol.ts:107
(anonymous) @ rpcProtocol.ts:303
e.fire @ event.ts:140
a @ ipc.net.ts:104
n._socketDataListener @ ipc.net.ts:133
emitOne @ events.js:116
emit @ events.js:211
addChunk @ _stream_readable.js:263
readableAddChunk @ _stream_readable.js:250
Readable.push @ _stream_readable.js:208
onread @ net.js:594
mainThreadExtensionService.ts:44 Error: Header must provide a Content-Length property.
    at StreamMessageReader.onData (/Users/guillaumedufour/.vscode/extensions/dufgui.vscode-tcl-0.0.1/node_modules/vscode-jsonrpc/lib/messageReader.js:200:27)
    at Socket.<anonymous> (/Users/guillaumedufour/.vscode/extensions/dufgui.vscode-tcl-0.0.1/node_modules/vscode-jsonrpc/lib/messageReader.js:185:19)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at Pipe.onread (net.js:594:20)
e.$onExtensionRuntimeError @ mainThreadExtensionService.ts:44
e._doInvokeHandler @ rpcProtocol.ts:261
e._invokeHandler @ rpcProtocol.ts:246
e._receiveRequest @ rpcProtocol.ts:192
e._receiveOneMessage @ rpcProtocol.ts:174
(anonymous) @ rpcProtocol.ts:107
(anonymous) @ rpcProtocol.ts:303
e.fire @ event.ts:140
a @ ipc.net.ts:104
n._socketDataListener @ ipc.net.ts:133
emitOne @ events.js:116
emit @ events.js:211
addChunk @ _stream_readable.js:263
readableAddChunk @ _stream_readable.js:250
Readable.push @ _stream_readable.js:208
onread @ net.js:594

Back to the top