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

Doesn't work in lambdas after v2.3.1 lambdas timeout without significant logs #533

Open
douglasg14b opened this issue Feb 21, 2025 · 0 comments

Comments

@douglasg14b
Copy link

Please read this entire template before posting any issue. If you ignore these instructions
and post an issue here that does not follow the instructions, your issue might be closed,
locked, and assigned the missing discussion label.

🐛 Bug Report

After upgrading from 2.2.7 to 2.3.1 error rates are 100% for lambdas. There are zero logs now.

Image

To Reproduce

Steps to reproduce the behavior:

Upgrade to v2.3.1

Expected behavior

It succeeds or fails with logs indicating the failure.

Your Environment

  • OS: Mac, Linux
  • Cloud Vendor: AWS
  • Turbo Version: 2.4.2
  • any other relevant information
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant