Ticket Created
2 months ago

SDK 8.0.0 BETA and language server build process

I tried using the SDK 8.0.0 BETA today and was able to get one smaller, more simple project working -- so I know the SDK works on my MacOS setup. However, I also ran into some issues, which seem to be specific to the language server build process (or whatever the process should be called):

1. One of my projects is able to get to 100% on the language server build processand displays warnings; however, when I attempt to run the app on the simulator, the process simply hangs. Sometimes it builds the PRG and sometimes it hangs prior. In both cases, the PRG never makes it to the simulator (whether it's already running or not). There's also no way to recover the build process and/or stop it; the little blue line continues to move at the top of the "Run and Debug" tab. The only way to stop this is to close the workspace/window. Whatever is going on also seems to cause an issue with "Find in Files", showing a subtext as "A system error occurred (spawn EBADF)".

2. Another project hangs around 33% during the language server build process, then seems to timeout and displays an error as such:

approachs7042mm: Error occurred while reading Monkey C file: Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null

In both the above cases, the projects compile and run just fine under SDK 7.4.3 and the older Monkey C plugin.

dbrobert
Parents
  • 2 months ago in reply to dbrobert

    If it's not running the build command, could you send us some logs? There's a setting for the Monkey C extension in VS Code 1.1.0 of "Debug Log Level". The higher the level of logging the easier it is for us to figure out what is going on, but you may not want to send us everything they include. At a minimum we would want the basic level, but the intermediate also includes the app's .mir file and verbose includes the .mc files.

Comment
  • 2 months ago in reply to dbrobert

    If it's not running the build command, could you send us some logs? There's a setting for the Monkey C extension in VS Code 1.1.0 of "Debug Log Level". The higher the level of logging the easier it is for us to figure out what is going on, but you may not want to send us everything they include. At a minimum we would want the basic level, but the intermediate also includes the app's .mir file and verbose includes the .mc files.

Children
  • 2 months ago in reply to Kyle.ConnectIQ

     There's no output because it's not even starting the process. The project seems to be unable to get through the language server build. After just shy of 5 minutes it seems to timeout and I see a bunch of Unmatched cancel warnings and an unsuccessful workspace build error.

    Jan. 10, 2025 12:40:22 P.M. org.eclipse.lsp4j.jsonrpc.RemoteEndpoint handleCancellation
    WARNING: Unmatched cancel notification for request id 14
    [Error - 12:40:22 PM] Full workspace build unsuccessful for root folder '/Users/douglas/develop/garmin/apps/boating'.

    After that, the "Problems" tab shows the error I mentioned already.


    approachs7042mm: Error occurred while reading Monkey C file: Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null