Replies: 1 comment
-
Same issue here |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The error happens randomly and without any steps that I can repeat to get it again. The approximate occurrence is 1 per 100 runs.
The Lighthouse is run in the AWS Fargate container (no parallel processes/threads). The custom code has the
try-catch
block however from the stack trace it seems the error eludes because thrown within the event listener, thus async.The problem here is not about the errors but about the inability to catch them and fail the Node process gracefully. Currently, I have to run Lighthouse in a subprocess to catch errors.
Lighthouse version: 9.0.0
Beta Was this translation helpful? Give feedback.
All reactions