-
Notifications
You must be signed in to change notification settings - Fork 378
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
"Network Error" when publishing a big Luis app #4294
Labels
Area: Publish
Bot Services
Required for internal Azure reporting. Do not delete. Do not change color.
customer-replied-to
Required for internal reporting. Do not delete.
customer-reported
Required for internal Azure reporting. Do not delete.
Type: Bug
Something isn't working
Comments
benbrown
added a commit
that referenced
this issue
Sep 29, 2020
…step which can take > 2 minutes for large models
cwhitten
added a commit
that referenced
this issue
Nov 17, 2020
* Fix #4294 - Disable the default timeout for requests on the LU build step which can take > 2 minutes for large models * update mocked request object to contain settimeout Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
EricDahlvang
pushed a commit
that referenced
this issue
Nov 27, 2020
* Fix #4294 - Disable the default timeout for requests on the LU build step which can take > 2 minutes for large models * update mocked request object to contain settimeout Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
benbrown
added a commit
to benbrown/BotFramework-Composer
that referenced
this issue
May 24, 2021
…oft#4295) * Fix microsoft#4294 - Disable the default timeout for requests on the LU build step which can take > 2 minutes for large models * update mocked request object to contain settimeout Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
benbrown
added a commit
that referenced
this issue
Jun 11, 2021
* Fix #4294 - Disable the default timeout for requests on the LU build step which can take > 2 minutes for large models * update mocked request object to contain settimeout Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
lei9444
pushed a commit
to lei9444/BotFramework-Composer-1
that referenced
this issue
Jun 15, 2021
* Fix microsoft#4294 - Disable the default timeout for requests on the LU build step which can take > 2 minutes for large models * Update main.yml Temporarily clearing the yarn cache trying to fix a CI build failure problem. * Update project.ts No idea why editing the workflow from GitHub caused this change, removing it. * Update main.yml * Update main.yml * Update main.yml * Update main.yml * Update main.yml * Update main.yml * Update main.yml * Update main.yml * Update main.yml * Trying if cache is good and clean * restoring the update of checksums * removing temp yarn cache clear * Update main.yml Restoring yarn cache clean Co-authored-by: Ben Brown <benbro@microsoft.com> Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
lei9444
pushed a commit
to lei9444/BotFramework-Composer-1
that referenced
this issue
Jun 15, 2021
…oft#4295) * Fix microsoft#4294 - Disable the default timeout for requests on the LU build step which can take > 2 minutes for large models * update mocked request object to contain settimeout Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Area: Publish
Bot Services
Required for internal Azure reporting. Do not delete. Do not change color.
customer-replied-to
Required for internal reporting. Do not delete.
customer-reported
Required for internal Azure reporting. Do not delete.
Type: Bug
Something isn't working
Describe the bug
When starting a bot using a .lu file with over 200 intents and over 6000 utterances, I get a Network error always in the call to "build" exactly after 2 minutes.
Luis app is created and version contains all intents, but the training didn't happen.
Version
Browser
OS
To Reproduce
Steps to reproduce the behavior:
Screenshots
The text was updated successfully, but these errors were encountered: