[24.1] Also check dataset.deleted when determining if data can be displayed #18547
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.
This is being called when serialising HDAs in the poller if the HDA is expanded.
When we purge via celery we set the HDA to deleted, flush and purge async, so it is possible that the async task removes the dataset from disk while the ORM object in the poller still is in non-purged state.
I think this fixes
https://sentry.galaxyproject.org/share/issue/0ae7a9d9ad564054bd11c9a43aa6994c/:
The error occurred at the same second as the last update to the history_dataset_association.
How to test the changes?
(Select all options that apply)
License