-
Notifications
You must be signed in to change notification settings - Fork 123
bf orchestrator:build incorrectly loads the lu file name and causing processing failure. #1332
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
lupart. e.g., the log shows Case#1Processed MyComposerSkill.en-usvs Case#2Processed 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#1D:\Env1\MyComposerSkill.en-us.bluvs Case#2D:\Env1\interruption\MyComposerSkill.en-us.lu.blu(interruptionfolder is the where the*.lufile locates specified in theluconfig)
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( |


