This repository was archived by the owner on Jan 15, 2025. It is now read-only.

Description
The following screenshots shows different behaviors for same command and input,
The BF CLI and node versions are all same as seen below.
bf orchestrator:build --model D:\Env1\orchestratorModels\english --luconfig D:\Env1\luConfigOrchestratorEnglish.json --debug

Problems
Different behaviors as seen in the screenshots below.
Appreciate if you could help to check, and at least we could understand the conditions and get a consistent behavior for our automation to rely on.
-
The log shows it is missing the lu part. e.g., the log shows Case#1 Processed MyComposerSkill.en-us vs Case#2 Processed MyComposerSkill.en-us.lu, which I suspect it's the reason.
-
The output behaviors are different
e.g., the snapshot is written to different paths, e.g., Case#1 D:\Env1\MyComposerSkill.en-us.blu vs Case#2 D:\Env1\interruption\MyComposerSkill.en-us.lu.blu (interruption folder is the where the *.lu file locates specified in the luconfig)
Case 1

Case 2

More Context
I managed to track down to this spot, but could not figure out further what could make the code run into different path.
|
public static async processLuContent( |