Skip to content
This repository was archived by the owner on Nov 30, 2022. It is now read-only.

Support for pausing an execution (Erasure Requests) #522

Closed
adriaaaa opened this issue May 17, 2022 · 0 comments · Fixed by #571
Closed

Support for pausing an execution (Erasure Requests) #522

adriaaaa opened this issue May 17, 2022 · 0 comments · Fixed by #571
Assignees
Labels
enhancement New feature or request

Comments

@adriaaaa
Copy link

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.

@adriaaaa adriaaaa added the enhancement New feature or request label May 17, 2022
@pattisdr pattisdr self-assigned this May 18, 2022
@pattisdr pattisdr changed the title Support for pausing an execution (Erasure Requests) #521 Support for pausing an execution (Erasure Requests) May 24, 2022
sanders41 pushed a commit that referenced this issue Jun 1, 2022
* 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.
sanders41 pushed a commit that referenced this issue Sep 22, 2022
* 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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants