-
Notifications
You must be signed in to change notification settings - Fork 366
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
Composer becomes unresponsive after logging into Azure to fetch LUIS key #7561
Comments
Cannot rerpro on a windows machine with the same build version on an organizational account |
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 |
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. |
I am not able to repro with my microsoft account. can try why personal account. |
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. |
Investigating root cause. Can't repro currently. |
@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. |
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:
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
The text was updated successfully, but these errors were encountered: