Composer becomes unresponsive after logging into Azure to fetch LUIS key

microsoft / BotFramework-Composer

Dialog creation and management for Microsoft Bot Framework Applications

https://docs.microsoft.com/en-us/composer/

MIT License

867 stars 369 forks source link

Composer becomes unresponsive after logging into Azure to fetch LUIS key #7561

Open emivers8 opened 3 years ago

emivers8 commented 3 years ago

Describe the bug

The app becomes mostly unresponsive after clicking to add LUIS key and logging in. The cursor changes on hover, and I can access the app menu, but I can't interact otherwise with the app. I've tested this with both core+language and assistant core templates.

Version

Version: 2.0.0-nightly.241915.204a82 Electron: 8.2.4 Chrome: 80.0.3987.165 NodeJS: 12.13.0 V8: 8.0.426.27-electron.0 macOS

To Reproduce

Steps to reproduce the behavior:

Open or create an assistant core or core with language bot
Click to add LUIS from rocket menu
Select existing resource and hit next
Complete Azure login
Composer becomes mostly unresponsive and doesn't move to the next screen in the modal

Expected behavior

I should be logged in and move onto the next screen in the modal and, like, be able to click stuff.

Additional context

I've gotten this consistently like six times in a row. I can't seem to get around it with today's build.

cc @Dewain27 @benbrown

pavolum commented 3 years ago

Cannot rerpro on a windows machine with the same build version on an organizational account

pavolum commented 3 years ago

Was able to repro with my personal @outlook azure account and a similar thing happens were the app goes unrepsonsive, I was able to get this error modal to appear after exiting and reentering the unresponsvie modal

benbrown commented 3 years ago

I cannot reproduce this. I don't think this has to do with the login - I think this is something going on with the webchat that seems to be logging lots of errors in the console.

sgellock commented 3 years ago

I am not able to repro with my microsoft account. can try why personal account.

emivers8 commented 3 years ago

It got to a point where Composer was just unresponsive when I tried to do anything. As Ben pointed out, it was logging the same error over and over in the debugging panel, which you can see in the screenshot I added to the OP. Rebooting my machine seems to have resolved the issue. I wondered if it might have had something to do with having gone through the LUIS/QnA key flow several times this morning. Maybe somehow got into a bad state or something. I was using my Microsoft account, though, not personal.

Dewain27 commented 3 years ago

Investigating root cause. Can't repro currently.

emivers8 commented 3 years ago

@xiyangdesign experienced this, as well: #7788

Would be good to explore cause in R14. If the state can't be prevented, maybe we can expose some kind of error or find an alternative to rebooting to correct.