I would like to have a server trigger mkc build commands programmatically and under child processes. This allows the server to handle requests for hex file generation concurrently.
I can make separate MakeCode project folders for each child on-the-fly, so no overlap there. However, they still all share the same cache and therefore occasionally I run into the issue where one process is updating the "updateCheckedAt" field in the -info file in the cache and another process is trying to read that file.
To achieve my goal of concurrent compilations without these occasional failures, I'll either need to disable the cache or lock the cache as a shared resource.
I would like to have a server trigger mkc build commands programmatically and under child processes. This allows the server to handle requests for hex file generation concurrently.
I can make separate MakeCode project folders for each child on-the-fly, so no overlap there. However, they still all share the same cache and therefore occasionally I run into the issue where one process is updating the "updateCheckedAt" field in the -info file in the cache and another process is trying to read that file.
To achieve my goal of concurrent compilations without these occasional failures, I'll either need to disable the cache or lock the cache as a shared resource.