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

Unexpected error: Cannot read property ‘startsWith’ of undefined #8368

Closed
scheyal opened this issue Jul 12, 2021 · 1 comment · Fixed by microsoft/botbuilder-js#3870
Closed
Assignees
Labels
P0 Must Fix. Release-blocker R14 Bugbash Type: Bug Something isn't working
Milestone

Comments

@scheyal
Copy link
Contributor

scheyal commented Jul 12, 2021

setup

  • simple node.js empty bot
  • add qna kb's luis dialog, orchestrator on top
  • few simple language intents, triggers

repro

Hit the duplicated intent recognized condition and then that error showed up (see visual below)

visual

error in emulator

image

bot general structure

image

@scheyal scheyal added Type: Bug Something isn't working Needs-triage A new issue that require triage R14 Bugbash labels Jul 12, 2021
@srinaath srinaath removed the Needs-triage A new issue that require triage label Jul 13, 2021
@srinaath srinaath added the P0 Must Fix. Release-blocker label Jul 15, 2021
@srinaath srinaath added this to the R14 milestone Jul 15, 2021
@taicchoumsft
Copy link
Contributor

The root cause was located in getTopScoringIntent, where it is possible in the nodejs version to return an undefined value. In the dotnet implementation the function always returns a string.

At some point, the CTRS (crosstrainedrecognizerset) IsRedirect function is called, which expects a string, causing the uncaught exception.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P0 Must Fix. Release-blocker R14 Bugbash Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants