COBOL Language Server output - New log ?

[FALLAI-Denis]

Hi,

In VS Code, I notice there is an output labeled "COBOL Language Server" that randomly activates (I assume when messages are produced).
Is it something new with Z Open Editor 3.1.0?

I have not captured the messages produced in this log and I have not succeeded in re-triggering their appearance.

This log is not necessarily easy to interpret.
Having looked at the IDz documentation, it seems to me that we can activate at will and configure the equivalent of this log.
Is it same for Z Open Editor (subset of IDz)?
Is there a way to intervene on its verbosity? trace certain particular events?

[FALLAI-Denis]

Sample of "COBOL Server Language Log":

[Error - 11:33:42] Request textDocument/documentSymbol failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\user\.vscodeMainframe\ibm.zopeneditor-3.1.0\dist\extension.js:14:1400101)
	at Object.dispose (c:\Users\user\.vscodeMainframe\ibm.zopeneditor-3.1.0\dist\extension.js:14:1463938)
	at c:\Users\user\.vscodeMainframe\ibm.zopeneditor-3.1.0\dist\extension.js:14:1460534
[Error - 11:33:42] Request textDocument/codeAction failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\user\.vscodeMainframe\ibm.zopeneditor-3.1.0\dist\extension.js:14:1400101)
	at Object.dispose (c:\Users\user\.vscodeMainframe\ibm.zopeneditor-3.1.0\dist\extension.js:14:1463938)
	at c:\Users\user\.vscodeMainframe\ibm.zopeneditor-3.1.0\dist\extension.js:14:1460534
[Error - 11:33:42] Request textDocument/documentLink failed.
Error: Connection got disposed.
	at Object.dispose (c:\Users\user\.vscodeMainframe\ibm.zopeneditor-3.1.0\dist\extension.js:14:1400101)
	at Object.dispose (c:\Users\user\.vscodeMainframe\ibm.zopeneditor-3.1.0\dist\extension.js:14:1463938)
	at c:\Users\user\.vscodeMainframe\ibm.zopeneditor-3.1.0\dist\extension.js:14:1460534

[phaumer]

@FALLAI-Denis VS Code's language server protocol implementation opens this automatically via the client when the server throws errors or writes messages. Perhaps these failures have to do with some of the performance tweaks we did in the last release. Were you closing editors when this happened?

[FALLAI-Denis]

Hi,

It seem to me that messages apppear when reopening a Git Repository with editors remaining opened when previously leaving this Repository.

[phaumer]

@FALLAI-Denis we made some improvements around the disposing the language client more reliably. Let us know if you still see the problem with v3.1.1.

[FALLAI-Denis]

For your information, log messages with ZOE v3.1.1:

[Error - 22:34:39] Request textDocument/documentHighlight failed.
  Message: Internal error.
  Code: -32603 
java.util.concurrent.CompletionException: java.lang.NullPointerException
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314)
	at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:645)
	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)
Caused by: java.lang.NullPointerException
	at com.ibm.wazi.lsp.cobol.core.handlers.DocumentHighlightHandler.computeOccurrences(DocumentHighlightHandler.java:46)
	at com.ibm.wazi.lsp.cobol.core.handlers.DocumentHighlightHandler.documentHighlight(DocumentHighlightHandler.java:102)
	at com.ibm.wazi.lsp.cobol.core.CobolLanguageServer.lambda$6(CobolLanguageServer.java:234)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
	... 6 more

The problem appears randomly.

[phaumer]

Thanks. This is a different - timing related - issue that we can address.

[phaumer]

We addressed these exceptions in Z Open Editor v3.2.0.