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

Can't see stack trace for server action errors #630

Open
landenai opened this issue Nov 18, 2024 · 2 comments
Open

Can't see stack trace for server action errors #630

landenai opened this issue Nov 18, 2024 · 2 comments

Comments

@landenai
Copy link
Contributor

landenai commented Nov 18, 2024

Note: unsure if this is an issue with our instrumentation or a limitation of using server actions

Environment

Steps to Reproduce:

Expected Result

  • In the trace we can see downstream spans related to the server action code and corresponding db calls
  • In the corresponding error, we see a relevant stack trace

Actual Results

  • We see a span for the server action with very little data like this
    Screenshot 2024-11-18 at 12 15 00 PM
  • The corresponding error does not show a stack trace
    Screenshot 2024-11-18 at 12 15 21 PM
@chargome
Copy link

This is likely the same issue as with #629 – the lambda in low-traffic applications is shutting down before the event flushes. Everything working as expected on a local prod build – we'll try to find a fix

@chargome
Copy link

I have also added #632 for future debugging purposes

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

2 participants