Skip to content

Intermittent NetworkError caused by TypeError in verification Lambda #8

@athewsey

Description

@athewsey

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?

[ERROR] TypeError: only size-1 arrays can be converted to Python scalars
Traceback (most recent call last):
  File "/var/task/app.py", line 52, in lambda_handler
    status_code, response = execute_if_token_is_valid(body['token'], challenge_id, verify_challenge, challenge_id)
  File "/var/task/app.py", line 68, in execute_if_token_is_valid
    return func(*args)
  File "/var/task/app.py", line 143, in verify_challenge
    state_manager.process(frame)
  File "/var/task/states/manager.py", line 19, in process
    success = self.current_state.process(frame)
  File "/var/task/states/nose.py", line 66, in process
    verified = self.verify_challenge(rek_landmarks, rek_pose, self.challenge_in_the_right)
  File "/var/task/states/nose.py", line 92, in verify_challenge
    trajectory_error = math.sqrt(residuals/len(self.nose_trajectory))

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions