This message was deleted.

There is an issue from a few days back about working on two stacks in parallel (await / async stuff), but code like this where everything happens serially is fine.

on a side note - would it be ok to use a node.cluster() to execute multiple stacks in parallell (as they would be in separate child processes)? https://nodejs.org/api/cluster.html

Further up this channel, maybe 3 or 4 days ago, there was a thread that mentioned a bit of shared internal memory ot config or something that caused problems when things were happening in parallel. I remember that @red-match-15116 was in the thread. And that's about all I know 🙂

So… the issue there was that

selectStack

and

createStack

change the currently selected stack which is a global setting (for a workspace). If these commands are executed in parallel in the same workspace they can have unexpected results and lead to odd bugs. I believe that if they are operating on separate workspaces this would not be a problem.

right - and that's not related to memory, that's related to something disk-physical I presume (or some pulumi temp workdir) outside of the process? with a node.cluster() it creates seperate nodejs instances (with seperate pids and memory) - so was hoping that might be enough to isolate the runs.

Yes, I understand that. But even in those separate processes if you end up running these commands on the same workspace you will run into these issues. Because exactly as you said, it’s not about memory but the physical files on disk. Essentially I’m saying using node.cluster() should be fine just be aware of the gotchas. It will only bite in very specific situations.