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

QnABot 5.4.3 fulfillment throws an exception when a Preprocessing Lambda Hook is configured. #651

Closed
2 tasks
rstrahan opened this issue Oct 20, 2023 · 2 comments
Assignees
Labels

Comments

@rstrahan
Copy link
Contributor

Describe the bug
QnABot 5.4.3 fulfillment throws an exception when a Preprocessing Lambda Hook is configured.

To Reproduce

Configure a Preprocessing Lambda Hook - it doesn't need to do anything - jest return event unchanged.
Then send an utterance to the bot from web client. It will not respond.
Check fulfillment function logs for the exception.

Expected behavior
Should function normally and not throw the exception.

Please complete the following information about the solution:

  • [v5.4.3 ] Version: [e.g. v0.0.1]

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0189) QnABot [...] v0.0.1".

  • [ALL ] Region: [e.g. us-east-1]
  • [No ] Was the solution modified from the version published on this repository?
  • If the answer to the previous question was yes, are the changes available on GitHub?
  • Have you checked your service quotas for the services this solution uses?
  • [YES - see image above ] Were there any errors in the CloudWatch Logs?

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
image

Additional context
Add any other context about the problem here.

Issue" the runPreProcessLambda function is broken (code).. When the preprocessor function is defined and run, the function returns an object with keys lambdaResultReq and lambdaResultRes.. But the keys need to be req and res.

@rstrahan rstrahan added the bug label Oct 20, 2023
@marcburnie marcburnie self-assigned this Oct 20, 2023
@marcburnie
Copy link
Member

Thanks for submitting this issue. This impacts v5.4.2 and v5.4.3 releases. We will close this ticket once a patch fix is available.

@marcburnie
Copy link
Member

This issue has been resolved in v5.4.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants