Root bot not starting (only skill bot does)
See original GitHub issueDescribe the bug
Faced this issue twice on my end while following the instructions to create and test a local skill The root bot keep showing that it’s starting but doesn’t, only the skill bot will start.
I get the same popup error message when I close and open the composer again for both the bots “Cannot read property ‘stdout’ of undefined” (error message reported: https://github.com/microsoft/BotFramework-Composer/issues/8547)
I’m running on dot net core version 5.0.302
Version
Version: 2.1.0 Electron: 8.2.4 Chrome: 80.0.3987.165 NodeJS: 12.13.0 V8: 8.0.426.27-electron.0
Browser
- Electron distribution
- Chrome
- Safari
- Firefox
- Edge
OS
- macOS
- Windows
- Ubuntu
To Reproduce
Steps to reproduce the behavior:
- Follow the steps in this documentation - Create and test a local skill
- Attempt to Test the bots locally
- The root bot will show as “starting” (been 30 mins now) but won’t start, only the skill bot will start
- After reopening composer, I receive this error message “Cannot read property ‘stdout’ of undefined”
Expected behavior
That I would be able to transition from the root bot to the skill bot as promised in the document
Screenshots
Additional context
Came across this bug the first time when my Greeting template resorted back to the default one (I was using the Core bot with Language template) after trying to start the bot. Got the same issue after repeating the steps on a test bot.
Would like to suggest to update the documentation after fixing. Will likely make an issue on composer-docs for tracing if it helps.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top GitHub Comments
@anusharr I had a similar issue where a running bot would hang forever and not give a valid error message. This PR (https://github.com/microsoft/BotFramework-Composer/pull/8587) adds a null check that enabled me to at least get a meaningful error message when the bot would not start.
@aninternetian once we get this null check shipped in our next patch in the coming weeks you should be able to see why your root bot wont start but your skill bot will. By any chance did you manually rename any of the bot files in the file system?
@aninternetian, thanks for reporting this. Let me attempt a repro on my end and update the thread with my findings.