Describe the bug
Normally, deleting a job's output history items causes the job to be deleted. If instead you use the "Select Items" multiselect to select a bunch of datasets by checkbox and then "With N Selected..." -> "Delete", the HDAs are marked deleted but the jobs are not. You can even undelete the HDAs and they'll complete normally when the job finishes.
Galaxy Version and/or server at which you observed the bug
Galaxy Version: 26.0
Commit: a4a3818
Browser and Operating System
Operating System: Linux
Browser: Firefox
To Reproduce
Steps to reproduce the behavior:
- Start a long running job
- Click the checkbox at the top of the history panel
- Select all of the job's outputs
- Click the action menu for the selected datasets
- Click "Delete"
- Click the trash can to show deleted datasets
- Observe that the job is still running on the backend
- Undelete the datasets
- Delete them individually using the trash can icon on each dataset
- Observe that the job is killed upon the deletion of the final dataset.
Expected behavior
Jobs are stopped when datasets are deleted.
Screenshots
N/A
Additional context
N/A
Describe the bug
Normally, deleting a job's output history items causes the job to be deleted. If instead you use the "Select Items" multiselect to select a bunch of datasets by checkbox and then "With N Selected..." -> "Delete", the HDAs are marked deleted but the jobs are not. You can even undelete the HDAs and they'll complete normally when the job finishes.
Galaxy Version and/or server at which you observed the bug
Galaxy Version: 26.0
Commit: a4a3818
Browser and Operating System
Operating System: Linux
Browser: Firefox
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Jobs are stopped when datasets are deleted.
Screenshots
N/A
Additional context
N/A