Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bf luis:version:export "\n" instead of line breaks #1307

Open
jane-bolton opened this issue Oct 19, 2021 · 4 comments
Open

bf luis:version:export "\n" instead of line breaks #1307

jane-bolton opened this issue Oct 19, 2021 · 4 comments
Assignees
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-replied-to Indicates that the team has replied to the issue reported by the customer. Do not delete. customer-reported Issue is created by anyone that is not a collaborator in the repository. needs-triage The issue has just been created and it has not been reviewed by the team.
Milestone

Comments

@jane-bolton
Copy link

Versions

  • What CLI version are you using.
    4.14.1
  • What Nodejs version are you using
    14.8.0
  • What command-line interpreters are you using
    CMD, Powershell
  • What OS are you using
    Windows 10

Describe the bug

bf luis:version:export --exportLU returns a .lu file with "\n" literal instead of actual line breaks. The file cannot be used until the "\n" are replaced with actual line breaks.

To Reproduce

Steps to reproduce the behavior:

  1. Run bf luis:version:export --exportLU... for an existing LUIS application
  2. View file
  3. All line breaks are removed and in their place, the literal string "\n" appears

Expected behavior

CLI command should return an immediately usable file.

Screenshots

Left-hand side shows the original file. Right-hand shows file after application is exported via CLI.
image

Additional context

This does not occur with the JSON CLI export, or when exporting from luis.ai

[bug]

@jane-bolton jane-bolton added 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. labels Oct 19, 2021
@dmvtech dmvtech added Bot Services Required for internal Azure reporting. Do not delete. Do not change color. customer-reported Issue is created by anyone that is not a collaborator in the repository. labels Oct 20, 2021
@carlosscastro
Copy link
Member

carlosscastro commented Oct 20, 2021

@munozemilio FYI. Could you please triage?

@carlosscastro
Copy link
Member

@munozemilio we talked offline, but please triage and assign release if this is something we can include in an upcoming release, or further troubleshoot if we need more info. Thanks!

@munozemilio munozemilio added this to the r16 milestone Oct 25, 2021
@munozemilio
Copy link
Member

Hello @jane-bolton thanks for reporting this, we will take this in the next release. In the meantime you can bypass this by piping the content directly to a file:

bf luis:version:export --exportLU  > lu_file_name.lu

@munozemilio munozemilio added the customer-replied-to Indicates that the team has replied to the issue reported by the customer. Do not delete. label Oct 28, 2021
@ashmit-github001
Copy link

@munozemilio
I'm facing the same issue, the flag --exportLU is not working for me. The command is still generating a json file. I had to explicitly mention file name with .lu extension to get a LU file.

Also the main issue is still same, the LU file generated is having \n in place of line breaks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-replied-to Indicates that the team has replied to the issue reported by the customer. Do not delete. customer-reported Issue is created by anyone that is not a collaborator in the repository. needs-triage The issue has just been created and it has not been reviewed by the team.
Projects
None yet
Development

No branches or pull requests

5 participants