running multiple compilations simultaneously in the same node process

[polamoros]

I tried this:

import path from "path";

import * as wing from "@winglang/compiler";

const wingfile1 = path.resolve("file1.w");
const wingfile2 = path.resolve("file2.w");

const compile = async (wingfile: string) => {
  const simfile = await wing.compile(wingfile, {
    target: wing.Target.SIM,
  });
  return simfile;
};

const testCompile = async () => {
  compile(wingfile1);
  compile(wingfile2);
  compile(wingfile1);
  compile(wingfile2);
};

testCompile();

file1.w

bring cloud;

let bucket = new cloud.Bucket() as "test1_bucket";
let queue = new cloud.Queue() as "test1_queue";
let api = new cloud.Api() as "test1_api";

file2.w

bring cloud;

let bucket = new cloud.Bucket() as "test2_bucket";

This happened:

the target/file2.wsim to contain the file1 compilations files.

target.zip

I expected this:

The compiler to compile the correct file.

Is there a workaround?

no

Component

Compiler

Wing Version

No response

Node.js Version

No response

Platform(s)

No response

Anything else?

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.

[skyrpex]

It doesn't happen if both consoles are created in different node processes.

I'm guessing there's a singleton-like functionality somewhere in the Wing SDK / Simulator... @Chriscbr Anything on top of your head that may be related to this issue?

[ainvoner]

in libs/wingcompiler/src/compile.ts there are several process.env usages and assignments. Since the compile command is async, we might overriding those values when running multiple compile commands rapidly in the same process?

[skyrpex]

We should be able to pass the necessary info using normal option objects instead of using process.env, right?

[Chriscbr]

@skyrpex @polamoros Could you create a repro that only uses @winglang/sdk or @winglang/compiler?

[polamoros]

Hey @Chriscbr, I tried calling the compiler multiple times with two different files, and it caused the target directory of file2 to contain the output of compiling file1.

(I'll upload the test I did later today)

[polamoros]

@Chriscbr I updated the issue description with the test I did using the compiler only.

[ekeren]

@polamoros, do you mind expressing the urgency here, I want to understand the priority here?

[polamoros]

@ekeren is not really urgent because we found a workaround and we were able to release the vs-code extension anyways.

It would be nice to fix it to be able to use the wingconsole/app package to run the console inside the vs-code extension instead of running a different node process for each console instance and also improving the integration between them.

[github-actions]

Hi,

This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days.
Feel free to re-open this issue when there's an update or relevant information to be added.
Thanks!

[github-actions]

Hi,

This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days.
Feel free to re-open this issue when there's an update or relevant information to be added.
Thanks!

[monadabot]

Congrats! 🚀 This was released in Wing 0.53.3.