1. 11 Feb, 2020 3 commits
    • Marco Trevisan's avatar
      tests/fprintd: Ensure that we get an error on early release · 8f35394b
      Marco Trevisan authored
      Ensure that we get an error when releasing a device that is in process of
      enrollment, verification or identification
      8f35394b
    • Marco Trevisan's avatar
      device: Cancel the ongoing operation when releasing the device · 4620c89c
      Marco Trevisan authored
      If a device is currently verifying, identifying or enrolling we may want the
      user to stop the operation before we actually release the device.
      
      Otherwise we may end-up in trying to close (failing) the internal device,
      while fprintd is still considering the device active, causing a dead-lock
      (the device can't be released, but neither claimed again or stop the current
      action).
      
      In fact calling Claim() -> EnrollStart() -> Release(), we would fail with
      the error
      
        net.reactivated.Fprint.Error.Internal:
        Release failed with error: The device is still busy with another
        operation, please try again later. (36)"
      
      However, if we try to call VerifyStop, after this error, we'd fail because
      for the fprintd logic, the device is not claimed anymore, but actually
      closed, and we'd need to claim it again, but... That would still cause an
      internal error.
      
      To avoid this, in case Relase() is called cancel the ongoing operation,
      and wait until it's done before completing the release call.
      4620c89c
    • Marco Trevisan's avatar
      device: Return 'verify-no-match' on cancelled operation · b1e6d829
      Marco Trevisan authored
      We were returning a 'verify-unknown-error' while we actually know what
      happened, so better to return a soft operation failure.
      b1e6d829
  2. 10 Feb, 2020 6 commits
  3. 07 Feb, 2020 2 commits
  4. 06 Feb, 2020 4 commits
  5. 05 Feb, 2020 25 commits