You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
** What went wrong?**
Not sure if this should be a feature or if it's a bug...
When using the useSeparateProcesses: true flag stack trace will be lost and you are left with Serverless: Failure [object Object].
What did you expect should have happened?
The stacktrace should be visible.
What was the config you used? useSeparateProcesses: true
What stacktrace or error message from your provider did you see?
There was none!
JNaeemGitonga
changed the title
useSeparateProcesses: true will swallow errorsuseSeparateProcesses: true will swallow errors (with javascript promises)
Jul 11, 2019
JNaeemGitonga
changed the title
useSeparateProcesses: true will swallow errors (with javascript promises)useSeparateProcesses: true will swallow errors (from javascript promises)
Jul 11, 2019
This is a Bug Report
Description
** What went wrong?**
Not sure if this should be a feature or if it's a bug...
When using the
useSeparateProcesses: true
flag stack trace will be lost and you are left withServerless: Failure [object Object]
.What did you expect should have happened?
The stacktrace should be visible.
What was the config you used?
useSeparateProcesses: true
What stacktrace or error message from your provider did you see?
There was none!
Similar or dependent issues:
Additional Data
This is the actual error there is no stacktrace
The text was updated successfully, but these errors were encountered: