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

Composer becomes unresponsive after creating and testing a bot #7788

Open
2 of 8 tasks
xiyangdesign opened this issue May 13, 2021 · 6 comments
Open
2 of 8 tasks

Composer becomes unresponsive after creating and testing a bot #7788

xiyangdesign opened this issue May 13, 2021 · 6 comments
Assignees
Labels
Build Bugbash P0 Must Fix. Release-blocker Type: Bug Something isn't working
Milestone

Comments

@xiyangdesign
Copy link

Describe the bug

Composer is having huge delay to any actions (e.g. click on buttons, resizing window, etc.) Web chat pane in the debugging window seems to be logging a lot. This is after I created a CoreWithLanguageUnderstanding bot, added a trigger and tested it.

I ran into this issue yesterday as well, without doing anything. Reinstalling Composer didn't help. (Restarting my laptop solved the issue)

See video below

Screen.Recording.2021-05-13.at.9.39.53.AM.mov

Version

image

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu

To Reproduce

Steps to reproduce the behavior:
Note: I ran into this issue yesterday as well, without doing anything. Reinstalling Composer didn't help. (Restarting my laptop solved the issue)

  1. Create a bot using CoreWithLanguageUnderstanding template
  2. Create a trigger, added an action: ask for user name
  3. Start bot
  4. Open webchat
  5. In the Webchat panel, click "restart conversation" a couple times quickly
  6. Error occurs
  7. Restart Composer sees another error (see screenshot)

image

Expected behavior

Screenshots

Additional context

@xiyangdesign xiyangdesign added Type: Bug Something isn't working Needs-triage A new issue that require triage Build Bugbash labels May 13, 2021
@emivers8
Copy link

repro of #7561

@darrenj
Copy link

darrenj commented May 13, 2021

Reproed on Windows too. Interestingly, when you reopen the project again it goes right back into the same loop of HTTP 500 errors!

@cwhitten
Copy link
Member

@darrenj were your repro steps exactly as @xiyangdesign 's?

1. Create a bot using CoreWithLanguageUnderstanding template
2. Create a trigger, added an action: ask for user name
3. Start bot
4. Open webchat
5. In the Webchat panel, click "restart conversation" a couple times quickly
6. Error occurs
7. Restart Composer sees another error (see screenshot)

@srinaath srinaath added this to the R13 milestone May 14, 2021
@srinaath srinaath added P0 Must Fix. Release-blocker and removed Needs-triage A new issue that require triage labels May 14, 2021
@sgellock
Copy link
Member

Shiproom - approved. @srinaath can you merge today, ASAP please.

@srinaath
Copy link
Contributor

Will do @sgellock

@cwhitten cwhitten modified the milestones: R13, R14 May 14, 2021
@cwhitten
Copy link
Member

Throttle PR merged, issue to be left open for additional investigation

@cwhitten cwhitten modified the milestones: R14, R15 Jun 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Bugbash P0 Must Fix. Release-blocker Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants