You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 30, 2022. It is now read-only.
* First draft - add ability to resume an erasure request by manually confirming the number of rows erased.
* Have the access and erasure endpoints share code.
* Update privacy request pause failure test.
* Add tests for erasure caching.
* Update both get_manual_count and get_manual_erasure_count to be inverses of cache_manual_input and cache_manual_erasure_count.
* Fix some formatting.
* Update changelog and add a docs draft.
* Assert that the access portion of execution isn't called if we submit the privacy request from the erasure step. Assert both access and erasure are called when we submit the privacy request from the access step.
* Fix submit mock.
* Respond to CR.
* First draft - add ability to resume an erasure request by manually confirming the number of rows erased.
* Have the access and erasure endpoints share code.
* Update privacy request pause failure test.
* Add tests for erasure caching.
* Update both get_manual_count and get_manual_erasure_count to be inverses of cache_manual_input and cache_manual_erasure_count.
* Fix some formatting.
* Update changelog and add a docs draft.
* Assert that the access portion of execution isn't called if we submit the privacy request from the erasure step. Assert both access and erasure are called when we submit the privacy request from the access step.
* Fix submit mock.
* Respond to CR.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Similar to #521 however, the scope of this ticket is focused on adding a node that can pause an ERASURE request and resume the request as needed.
The text was updated successfully, but these errors were encountered: