This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
Bug: Getting Access Request Results from Cache #1348
Assignees
Labels
bug
Something isn't working
Comments
10 tasks
sanders41
pushed a commit
that referenced
this issue
Sep 20, 2022
#1349) * Fix bug where erasure count confirmations may be returned instead of selected access request results when attempting to get access requests from the cache. Because erasure requests are run after access requests, there normally isn't erasure results in the cache when we attempt to get access results. However, if we were retrying a privacy request from a checkpoint that had already erased data, we could possibly return erasure results instead of access results, depending on if the access or erasure key was accessed last. * Update CHANGELOG.
sanders41
pushed a commit
that referenced
this issue
Sep 22, 2022
#1349) * Fix bug where erasure count confirmations may be returned instead of selected access request results when attempting to get access requests from the cache. Because erasure requests are run after access requests, there normally isn't erasure results in the cache when we attempt to get access results. However, if we were retrying a privacy request from a checkpoint that had already erased data, we could possibly return erasure results instead of access results, depending on if the access or erasure key was accessed last. * Update CHANGELOG.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug Description
When retrying a privacy request from failure, it is possible that we retrieve some erasure counts instead of access results for some of the collections.
This bug is unlikely to have been hit so far, but could result in the incorrect values being returned for an access request.
Steps to Reproduce
Expected behavior
A description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: