Mohsen Ansari

Hey @ravishankar82 did you try re-deploying or deploying in another region just to confirm the issue persists? We have a [known behavior](https://github.com/aws-solutions/aws-qnabot#known-behavior) where the custom resource creating OpenSearch resources times...

Strange that lexv2-build didn't run make. It might have something to do with python configuration. There is a string chance that npm run up attempted to build for lexv2-build and...

Hey @antonykattarath thanks for notifying us about this. I looked through the source code. Seems like you are right. We'll have to do some testing with `LambdaAccessRole` removed to make...

Hi @ChaseIngebritson the action `lex:RecognizeText` is LexV2 specific so it shouldn't interfere with V1 roles. Thanks for bringing this up. I'm looking into recreating this and will update this thread...

Hi @Spartan27 thanks for bringing this up. As you mentioned, at the moment we only have the solution as a CloudFormation Stack. There is a plan to rebuild the architecture...

Hey @melpais Thanks for reporting this bug. We noticed this bug because of a Lambda Layer (QnABotCommonLambdaLayer) that was missing in the new version, hence seeing `Cannot find module qnabot/logging`....

> @mohsenari sorry for delay on reviewing this. What did we decide in the demo? Should I take a look? @mikeland86 no worries. We decided to pause this until we...

@pomdtr That's a great suggestion. We've been looking into integrating with `direnv` for the past couple weeks. You suggestion technically works but it also makes `devbox` think it's in a...

@methyl We're looking into VSCode integration with `direnv + devbox` as well. If we can't get the extension to work with a devbox environment as we intend, we might have...

@methyl We published a [devbox extension for VSCode](https://marketplace.visualstudio.com/items?itemName=jetpack-io.devbox&ssr=false#overview). It detects if you have devbox.json and when you open terminal in the IDE, it automatically goes to devbox shell. Feel free...