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

Lambda Resolver - Top Level Errors not being logged in amplify mock #6311

Closed
benbrunyee opened this issue Jan 5, 2021 · 2 comments
Closed
Labels
feature-request Request a new feature mock Issues tied to the mock functionality pending-release Code has been merged but pending release

Comments

@benbrunyee
Copy link

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
When requiring an invalid package, the function will simply timeout with no indication of what the error is.

Amplify CLI Version
4.41.0

To Reproduce

  1. In your lambda resolver, provide an invalid require statement before the handler is defined.
  2. Run amplify mock
  3. Execute the graphql query/mutation that uses said lambda resolver

Expected behavior
Print the error in the console and fail. Not timeout.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Windows
  • Node Version: v12.16.1
@edwardfoyle edwardfoyle added enhancement mock Issues tied to the mock functionality labels Jan 5, 2021
@edwardfoyle edwardfoyle added the pending-release Code has been merged but pending release label Feb 12, 2021
@edwardfoyle
Copy link
Contributor

The fix for this has been released in the latest version of the CLI. Please upgrade to the latest version to try it out.

@github-actions
Copy link

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 25, 2021
@josefaidt josefaidt added feature-request Request a new feature and removed enhancement labels Sep 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request a new feature mock Issues tied to the mock functionality pending-release Code has been merged but pending release
Projects
None yet
Development

No branches or pull requests

3 participants