Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unable to execute the bot on Azure functions
See original GitHub issueDescribe the bug
Upon publishing the bot to Azure function, the Azure function goes down and doesnt respond to any request
I have followed the steps for publishing bot to Azure Function with resources created through the command line script
The Function App shows up the below error
And the status of the runtime shows as error
And the diagnosis says
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: b3462131-c17c-c9e1-106c-390e0bdb523d
- Version Independent ID: bd203f82-3725-6df6-1aef-9ffad92fa7fa
- Content: Publish a bot to Azure - Bot Composer
- Content Source: composer-docs/how-to-publish-bot.md
- Service: bot-composer
- GitHub Login: @zxyanliu
- Microsoft Alias: kamrani
Version
1.1.1
Browser
Chrome
- Electron distribution
- Chrome
- Safari
- Firefox
- Edge
OS
- macOS
- Windows
- Ubuntu
To Reproduce
Follow steps for Azure function as provided here https://docs.microsoft.com/en-us/composer/how-to-publish-bot
Expected behavior
The function should not error and the bot should reply over the bot channel registration test panel
Screenshots
Added above at relevant place
Additional context
The function apps were created through the commandline script as provided in the documentation
Issue Analytics
- State:
- Created 3 years ago
- Comments:18 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
If you check PR #4570 , it captures the fix to make functions work again and some improvements to have it work in more environemnts. Options to get this fix are 1) wait for the next composer release or 2) eject your runtime and apply that fix to unblock right away. I’d wait until the PR is closed to adopt the fix to make sure we are happy with the final code.
Was able to reproduce the bug. I’ll work on a fix, most likely will go out on the next release of composer in early Nov. However once the change hits main, you could use composer from nightly build or from source. If the change only affects the runtime, then you could just update your runtime without updating composer. I won’t be sure of the exact scope of the fix until I finish it. I’ll update with details on how to get access when that happens.