-
Notifications
You must be signed in to change notification settings - Fork 40
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
Intermittent NetworkError caused by TypeError in verification Lambda #8
Comments
Hi. Yes, you're right regarding why errors manifest as |
I am facing the same problem, how can it be solved? |
I appreciate this might not be that useful, but I think the issue lies in The math |
Based on the info here: https://stackoverflow.com/a/26438018/402585 It does seem to work if you change the code in
|
I ran to this issue and the change suggested by @eddturtle fixed the issue. |
Hi folks,
I've been seeing an intermittent issue which manifests as
NetworkError
in the front end, but the underlying cause seems to be an unhandled exception in the verification Lambda (because CORS headers don't get set on the error response through API Gateway, so the issue appears as a CORS/network issue on browser side).Stack trace below but I haven't had chance to dig in to it yet - I wonder if there's something about the number of frames uploaded for the check that can affect the dimensionality of the variable in question?
The text was updated successfully, but these errors were encountered: