{{ message }}
Repository navigation
Cannot fall back to JS-based CLS when native binary fails to start #116
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Feedback source
None
GitHub Copilot plugin version
0.16.0.202604020254
Eclipse IDE and version
Eclipse Platform 2025-09 with ABAP Development Tools
Platform
Microsoft Windows NT 10.0.22631.0 x64
Node v24.11.1
Steps to reproduce
- Have a group policy in place that forbids execution of
.exefiles in %AppData%, which is where Eclipse plugins reside in our installation - Use a fresh Eclipse installation with the Marketplace Client
- Install GitHub Copilot 0.16 from the Eclipse Marketplace
- Restart Eclipse
- Confirm Copilot quick start window
- Face the below described "actual behavior"
Logs (optional)
!ENTRY com.microsoft.copilot.eclipse 1 0 2026-04-10 11:02:16.497
!MESSAGE [Info] Starting language server with binary lsp agent.
!ENTRY com.microsoft.copilot.eclipse 1 0 2026-04-10 11:02:16.501
!MESSAGE [Info] Found native binary in fragment bundle: com.microsoft.copilot.eclipse.core.agent.win32
!ENTRY org.eclipse.lsp4e 4 0 2026-04-10 11:02:18.141
!MESSAGE java.lang.IllegalStateException: Input stream must be configured.
!STACK 0
java.util.concurrent.CompletionException: java.lang.IllegalStateException: Input stream must be configured.
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:791)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1773)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
Caused by: java.lang.IllegalStateException: Input stream must be configured.
at org.eclipse.lsp4j.jsonrpc.Launcher$Builder.create(Launcher.java:310)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$1(LanguageServerWrapper.java:435)
at java.base/java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:787)
... 8 more
!ENTRY com.microsoft.copilot.eclipse 4 0 2026-04-10 11:02:18.142
!MESSAGE [Error] java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.IllegalStateException: Input stream must be configured.
!STACK 0
java.util.concurrent.CompletionException: java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.IllegalStateException: Input stream must be configured.
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:994)
at java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:974)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1773)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
Caused by: java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.IllegalStateException: Input stream must be configured.
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$9(LanguageServerWrapper.java:475)
at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:990)
... 9 more
Caused by: java.util.concurrent.CompletionException: java.lang.IllegalStateException: Input stream must be configured.
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:791)
... 8 more
Caused by: java.lang.IllegalStateException: Input stream must be configured.
at org.eclipse.lsp4j.jsonrpc.Launcher$Builder.create(Launcher.java:310)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$1(LanguageServerWrapper.java:435)
at java.base/java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:787)
... 8 more
!ENTRY org.eclipse.lsp4e 4 0 2026-04-10 11:02:18.148
!MESSAGE java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.IllegalStateException: Input stream must be configured.
!STACK 0
java.util.concurrent.CompletionException: java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.IllegalStateException: Input stream must be configured.
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:994)
at java.base/java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:974)
at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:510)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1773)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
Caused by: java.lang.RuntimeException: java.util.concurrent.CompletionException: java.lang.IllegalStateException: Input stream must be configured.
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$9(LanguageServerWrapper.java:475)
at java.base/java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:990)
... 9 more
Caused by: java.util.concurrent.CompletionException: java.lang.IllegalStateException: Input stream must be configured.
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:791)
... 8 more
Caused by: java.lang.IllegalStateException: Input stream must be configured.
at org.eclipse.lsp4j.jsonrpc.Launcher$Builder.create(Launcher.java:310)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$1(LanguageServerWrapper.java:435)
at java.base/java.util.concurrent.CompletableFuture$UniRun.tryFire(CompletableFuture.java:787)
... 8 more
!ENTRY com.microsoft.copilot.eclipse 4 0 2026-04-10 11:02:18.274
!MESSAGE [Error] Failed to load built-in modes
!STACK 0
java.util.concurrent.CompletionException: java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.listModes(com.microsoft.copilot.eclipse.core.lsp.protocol.ConversationModesParams)" because "server" is null
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1159)
at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.listModes(com.microsoft.copilot.eclipse.core.lsp.protocol.ConversationModesParams)" because "server" is null
at com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServerConnection.lambda$18(CopilotLanguageServerConnection.java:379)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$17(LanguageServerWrapper.java:982)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
... 4 more
!ENTRY com.microsoft.copilot.eclipse 4 0 2026-04-10 11:02:18.279
!MESSAGE [Error] Failed to load custom modes from LSP
!STACK 0
java.util.concurrent.CompletionException: java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.listModes(com.microsoft.copilot.eclipse.core.lsp.protocol.ConversationModesParams)" because "server" is null
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1159)
at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.listModes(com.microsoft.copilot.eclipse.core.lsp.protocol.ConversationModesParams)" because "server" is null
at com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServerConnection.lambda$18(CopilotLanguageServerConnection.java:379)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$17(LanguageServerWrapper.java:982)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
... 4 more
!ENTRY com.microsoft.copilot.eclipse 4 0 2026-04-10 11:02:18.299
!MESSAGE [Error] java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.registerTools(com.microsoft.copilot.eclipse.core.lsp.protocol.RegisterToolsParams)" because "server" is null
!STACK 0
java.util.concurrent.CompletionException: java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.registerTools(com.microsoft.copilot.eclipse.core.lsp.protocol.RegisterToolsParams)" because "server" is null
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1159)
at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.registerTools(com.microsoft.copilot.eclipse.core.lsp.protocol.RegisterToolsParams)" because "server" is null
at com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServerConnection.lambda$24(CopilotLanguageServerConnection.java:432)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$17(LanguageServerWrapper.java:982)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
... 4 more
!ENTRY com.microsoft.copilot.eclipse 4 0 2026-04-10 11:02:18.368
!MESSAGE [Error] java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.registerTools(com.microsoft.copilot.eclipse.core.lsp.protocol.RegisterToolsParams)" because "server" is null
!STACK 0
java.util.concurrent.CompletionException: java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.registerTools(com.microsoft.copilot.eclipse.core.lsp.protocol.RegisterToolsParams)" because "server" is null
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1159)
at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.NullPointerException: Cannot invoke "com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServer.registerTools(com.microsoft.copilot.eclipse.core.lsp.protocol.RegisterToolsParams)" because "server" is null
at com.microsoft.copilot.eclipse.core.lsp.CopilotLanguageServerConnection.lambda$24(CopilotLanguageServerConnection.java:432)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$17(LanguageServerWrapper.java:982)
at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:1150)
... 4 more
!ENTRY com.sap.adt.util 1 0 2026-04-10 11:02:18.539
!MESSAGE try to find keystore(s) of operating system
!ENTRY com.sap.adt.util 1 0 2026-04-10 11:02:18.575
!MESSAGE successfully loaded keystore "Windows-ROOT"
!ENTRY com.sap.adt.util 1 0 2026-04-10 11:02:18.622
!MESSAGE successfully loaded keystore "Windows-MY"
Expected behavior
Falling back to node-based LSP, like in this log output from 0.15:
!ENTRY com.microsoft.copilot.eclipse 1 0 2026-04-10 10:34:07.602
!MESSAGE [Info] Starting language server with binary lsp agent.
!ENTRY com.microsoft.copilot.eclipse 1 0 2026-04-10 10:34:07.605
!MESSAGE [Info] Found native binary in fragment bundle: com.microsoft.copilot.eclipse.core.agent.win32
!ENTRY com.microsoft.copilot.eclipse 4 0 2026-04-10 10:34:09.228
!MESSAGE [Error] Binary LSP agent start failed. Retrying with JS agent.
!STACK 0
java.io.IOException: Cannot run program "<redacted>\installation\2025-09\configuration\org.eclipse.osgi\793\0\.cp\copilot-agent\copilot-language-server.exe": CreateProcess error=1260, This program is blocked by group policy. For more information, contact your system administrator
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1188)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1105)
at org.eclipse.lsp4e.server.ProcessStreamConnectionProvider.start(ProcessStreamConnectionProvider.java:58)
at com.microsoft.copilot.eclipse.core.lsp.LsStreamConnectionProvider.startBinaryLspAgent(LsStreamConnectionProvider.java:85)
at com.microsoft.copilot.eclipse.core.lsp.LsStreamConnectionProvider.start(LsStreamConnectionProvider.java:68)
at org.eclipse.lsp4e.LanguageServerWrapper.lambda$0(LanguageServerWrapper.java:399)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
Caused by: java.io.IOException: CreateProcess error=1260, This program is blocked by group policy. For more information, contact your system administrator
at java.base/java.lang.ProcessImpl.create(Native Method)
at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:516)
at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:161)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1142)
... 12 more
!ENTRY com.sap.adt.util 1 0 2026-04-10 10:34:09.635
!MESSAGE try to find keystore(s) of operating system
!ENTRY com.sap.adt.util 1 0 2026-04-10 10:34:09.662
!MESSAGE successfully loaded keystore "Windows-ROOT"
!ENTRY com.microsoft.copilot.eclipse 1 0 2026-04-10 10:34:09.698
!MESSAGE [Info] JS agent started successfully.
Actual behavior
After startup, we get this error message:

This causes Copilot to be not usable.
More can be found in the logs above.
Additional information
Could probably be worked around if a solution for #53 was in place.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Type
Projects
Milestone
Relationships
Development
Issue actions
You can’t perform that action at this time.

Activity
jdneo commentedon Apr 10, 2026
Wired. We did not change the launch logic. But why this time the binary cls dies not throw the permission error? Did you change the installation location?
MergingMonkey commentedon Apr 15, 2026
No, the installation location is the same in both cases. Same machine too.
jdneo commentedon Apr 22, 2026
I'm not sure if it is related with the node runtime search. The current implementation will not search for the os installation location at first -> causing find a node js runtime which cannot meet the requirement.
I'll try to make some fix and release a nightly build. Will inform you once it is available.
jdneo commentedon Apr 23, 2026
@MergingMonkey Could you please try the latest nightly? https://marketplace.eclipse.org/content/github-copilot-nightly
MergingMonkey commentedon Apr 23, 2026
@jdneo
Thanks, I just tried with 0.16.0.202604230218_nightly, previously uninstalling 0.15. Still the same symptoms.
Logs:
jdneo commentedon Apr 23, 2026
Wired, from the logs seems that it does not fallback to the js language server.
Because I did not see
!MESSAGE [Error] Binary LSP agent start failed. Retrying with JS agent.in the log.Is that possible that the binary language server is allowed to run but immediately killed?
Could you check if there is any nodejs process (the copilot language server process) running after starting Eclipse?
MergingMonkey commentedon May 8, 2026
0.15 (working version):

The node is started from a
.nodefolder in the installation directory - I didn't know that until now!I assume this Node installation comes from the Node.js embedder from Wild Web Developer 1.2.1:

I knew that this plugin was necessary to install to get Copilot working at all in our environment. Because if it is not installed, we get an error too:
Here's the log from 0.15 without Node.js embedder from Wild Web Developer ("!ENTRY com.microsoft.copilot.eclipse 4 0 2026-05-08 10:33:15.004" is interesting):
So, 0.15 doesn't use the system's node, but can be worked around with Node.js embedder from Wild Web Developer. For 0.16 upwards, this workaround doesn't work.
0.17 doesn't spawn a Node.js instance either, just like 0.16. Which is very sad because 0.17 seems to bring some interesting improvements for ABAP (thanks for that by the way).
My node installation can be found in Windows Command Prompt and Powershell - so it is available from PATH:
Why wouldn't 0.15 find it then? Maybe it's a hint at the root cause for all of this.
MergingMonkey commentedon May 8, 2026
Regarding your first question ("Is that possible that the binary language server is allowed to run but immediately killed?"):
I cannot confirm this 100%, but if I extract the .exe and start it, it will not be shown in the task manager, and I get this pop-up:
jdneo commentedon May 8, 2026
Where do you install the node?
We search several places to find the node installation, See:
copilot-for-eclipse/com.microsoft.copilot.eclipse.core/src/com/microsoft/copilot/eclipse/core/lsp/NodeJsManager.java
Lines 65 to 80 in 0be3112
MergingMonkey commentedon May 8, 2026
It's at
C:\Program Files\nodejs\node.exe, so the exact path that is searched ingetDefaultNodePathcalled bygetNodeFromDefaultLocationas the last fallback. So it should find it.But that's the issue in 0.15.
In 0.16+, the fallback to NodeJS isn't even tried according to logs.
MergingMonkey commentedon May 8, 2026
Gemini and Claude might have found the issue in LsStreamConnectionProvider.java:
copilot-for-eclipse/com.microsoft.copilot.eclipse.core/src/com/microsoft/copilot/eclipse/core/lsp/LsStreamConnectionProvider.java
Lines 70 to 88 in 0be3112
On Windows, when startBinaryLspAgent() throws IOException, the inner catch swallows it without rethrowing. The outer catch is never triggered, startJsLspAgent() is never called, and lsp4e then fails with "Input stream must be configured" because the streams are never set up.
I wonder why this Linux workaround is even in place, since the comment refers to exactly this issue, which is created for Windows.
jdneo commentedon May 8, 2026
@MergingMonkey Your analysis seems right. Let me make a fix.
[-]0.16 does not fall back to JS-based LSP when native binary fails to start[/-][+]Cannot fall back to JS-based LSP when native binary fails to start[/+][-]Cannot fall back to JS-based LSP when native binary fails to start[/-][+]Cannot fall back to JS-based CLS when native binary fails to start[/+]jdneo commentedon May 9, 2026
@MergingMonkey A nightly build released. Please check if the problem is solved.
Meanwhile, feel free to let us know your feedback about abap development in 0.17.0.
MergingMonkey commentedon May 12, 2026
@jdneo
Yes, it works :)
and finally:
Thank you for the quick fix!
Looking forward to testing the new ABAP improvements in the next days.