search

microsoft / botbuilder-tools

Welcome to the Bot Framework Tools repository, which is the home for a set of tools for developers building bots with the Microsoft Bot Framework
https://github.com/Microsoft/botframework
MIT License
444 stars 262 forks source link

Getting error while exporting from remote to local #1388

Closed SreekanthOAuth closed 4 years ago

SreekanthOAuth commented 4 years ago

Tool

Name: QnAMaker Version: 1.3.2 OS: Windows 10

Describe the bug

Today, while trying export command getting below error,

`Sorry, unable to parse stdin as JSON!

{}

Stopping further processing.`

To Reproduce

Steps to reproduce the behavior:

  1. Create QnA Model
  2. Export Sample Assistant from here
  3. And update cognitive models with KB model
  4. Run the update_cognitive_models.ps1

Expected behavior

Should export the .lu file.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

[bug]

dmvtech commented 4 years ago

I'm seeing if I can reproduce this issue. I'll let you know if I have any questions.

dmvtech commented 4 years ago

I believe this is related to https://github.com/microsoft/botframework-solutions/issues/2689

SreekanthOAuth commented 4 years ago

@dmvtech , Tried based on the above link and now getting below exception,

Sorry, error parsing file as QnA JSON: D:\Test-Chatbot\test-new\test\src\virtualAssistant\deployment\scripts..\resources\QnA\en\myskill.qna Stopping further processing.

Could you please look into it.

Thanks, Sreekanth

darrenj commented 4 years ago

I believe this might be related to a recent change in qnamaker CLI around the deprecated message. To prove this could you install 1.3.1 directly and see if you can repro please?

npm install qnamaker@1.3.1

darrenj commented 4 years ago

I have reproed the issue with qnamaker@1.3.2, regressing to @1.3.1 resolved the issue for me.

a-b-r-o-w-n commented 4 years ago

@SreekanthOAuth qnamaker@1.3.3 was released on Friday which we believe fixes this issue. Can you please try that version and let us know if the issue is fixed? If not, please re-open this issue.

SreekanthOAuth commented 4 years ago

@a-b-r-o-w-n , thanks for the update and will let you know if we see any issues.