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

bf orchestrator:build incorrectly loads the lu file name and causing processing failure. #1332

@dawwa

Description

@dawwa

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

image

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
image

Case 2
image

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(

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIndicates an unexpected problem or an unintended behavior.needs-triageThe issue has just been created and it has not been reviewed by the team.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions