fix lu build bug when training empty intents #643
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boydc2014
approved these changes
Mar 9, 2020
There was a problem hiding this comment.
LGTM, @munozemilio i'm approving and merging this, since it's a P0 bug in composer on this, and this is a very minor fix, let us know if you have any concerns.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix two bugs:
[WARN]: empty intent(s) # A, # B are filtered when handling luis application[WARN]: Invalid model info found. Skipping "> !# @enableSections = truewhich was false error.enableSectionsis used in luParser.js. The fix here is to avoid the error message.