bf orchestrator:build incorrectly loads the lu file name and causing processing failure. #1332
Labels
bug
Indicates an unexpected problem or an unintended behavior.
needs-triage
The issue has just been created and it has not been reviewed by the team.
The following screenshots shows different behaviors for same command and input,
The BF CLI and node versions are all same as seen below.
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#1Processed MyComposerSkill.en-us
vs 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#1
D:\Env1\MyComposerSkill.en-us.blu
vs Case#2D:\Env1\interruption\MyComposerSkill.en-us.lu.blu
(interruption
folder is the where the*.lu
file locates specified in theluconfig
)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.
botframework-cli/packages/orchestratorlib/src/orchestratorhelper.ts
Line 1214 in 693b1a0
The text was updated successfully, but these errors were encountered: