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

     I've now narrowed the issue down to, at least for this project, whether or not the language server build process happens incidentally on project opening before building/running the app first. That is, if I open the project and there are no previously open files (or none that are Monkey C specific), then the Monkey C Language Server is not triggered. I then immediately go to the "Run and Debug" tab and run the app. I'm prompted to select a device, the language server starts, the app builds and the PRG is pushed to the simulator. At this point, because the language server build process has worked, everything works as expected. However, if I leave a Monkey C source file open as the active editing tab, close Visual Studio Code, let all the associated process stop, and restart VSC, then I see that String.split Java error as soon as the language server build process starts.

    I'm unable to replicate this with any other projects (so far) but I will try to narrow it down further. Is there anything else I can do, short of giving you the source tree that may provide further insight?

Comment
  • 2 months ago

     I've now narrowed the issue down to, at least for this project, whether or not the language server build process happens incidentally on project opening before building/running the app first. That is, if I open the project and there are no previously open files (or none that are Monkey C specific), then the Monkey C Language Server is not triggered. I then immediately go to the "Run and Debug" tab and run the app. I'm prompted to select a device, the language server starts, the app builds and the PRG is pushed to the simulator. At this point, because the language server build process has worked, everything works as expected. However, if I leave a Monkey C source file open as the active editing tab, close Visual Studio Code, let all the associated process stop, and restart VSC, then I see that String.split Java error as soon as the language server build process starts.

    I'm unable to replicate this with any other projects (so far) but I will try to narrow it down further. Is there anything else I can do, short of giving you the source tree that may provide further insight?

Children
No Data