Adding syncronous delete method for environment builds #107
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
costrouc
force-pushed
the
syncronous-delete
branch
11 times, most recently
from
8654ea9
to
584e271
Compare
costrouc
force-pushed
the
syncronous-delete
branch
from
584e271
to
6c49952
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the delete button trigger a task to delete the given build. The major problem with this is that when the user clicks delete the environment is not deleted immediately (this isn't possible so we have to mark the build for deletion). Then a task is kicked off to delete the given build. A conda_store configuration setting is available for users to choose which build artifacts are deleted.