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

Unable to successfully publish to LUIS (sometimes) #2195

Closed
cwhitten opened this issue Mar 7, 2020 · 2 comments
Closed

Unable to successfully publish to LUIS (sometimes) #2195

cwhitten opened this issue Mar 7, 2020 · 2 comments
Assignees
Labels
P0 Must Fix. Release-blocker Type: Bug Something isn't working

Comments

@cwhitten
Copy link
Member

cwhitten commented Mar 7, 2020

After creating an initial LU application and then publishing updated model data associated with input lu, I see the following and can no longer successfully publish:

[WARN]: Invalid model info found. Skipping "> !# @enableSections = true"
POST /api/projects/opened/luFiles/publish 200 21600.032 ms - -
(node:75647) UnhandledPromiseRejectionWarning: Error: The application cannot be published. One or more models in the application version require training.
    at new RestError (/Users/chriswhitten/src/BotFramework-Composer/Composer/node_modules/@azure/ms-rest-js/dist/msRest.node.js:2400:28)
    at /Users/chriswhitten/src/BotFramework-Composer/Composer/node_modules/@azure/ms-rest-js/dist/msRest.node.js:3544:37
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:75647) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 9)

Steps to repro:

  1. Create Bot w/ LUIS recognizer
  2. Create Intent trigger and Intent definition
  3. Inside Trigger flow, create new Prompt and provide labeled utterances for entity extraction
  4. Repeat 1-2 times, eventually see error.
  5. Once in this state, seems unable to recover
@cwhitten cwhitten added Type: Bug Something isn't working P0 Must Fix. Release-blocker Needs-triage A new issue that require triage labels Mar 7, 2020
@boydc2014
Copy link
Contributor

boydc2014 commented Mar 9, 2020

@cwhitten after some investigation, this is an issue when user have an intent with no utterances in it. This is an interface change in LUIS service api that don't allow empty intent anymore. LUIS api accept empty intent when creating intents, but will return error when train an application, this is the reason that make this issue seems "not recoverable".

Anyhow, @feich-ms will do a fix in bf-cli side, that issue a warning when empty intent found, and filter empty before publishing, then @lei9444 will pick that up.

Thanks @lei9444 and @feich-ms. It takes some time to reproduce :)

@cwhitten
Copy link
Member Author

cwhitten commented Mar 9, 2020

addressed via #2201

@cwhitten cwhitten closed this as completed Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 Must Fix. Release-blocker Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants