-
Notifications
You must be signed in to change notification settings - Fork 999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dataset not visible in a user's history (compressed/uncompressed, same hid) #17220
Comments
@ahmedhamidawan I think you fixed this in 84b6272 |
Yes @mvdbeek , thank you! |
Hmm, guess that wasn't all of it, here's a history with duplicate hids from an implicit conversion: with API https://usegalaxy.org/api/histories/c845ae1a2747ea06/contents |
For that history for e.g., I was able to come up with a solution where we add a sub_items_in_history.mp4I will open a PR tomorrow for this |
This looks cool, but the original dataset is the one you'd want to see by default |
How does it show in the toolform dataset input? |
Oh that would show the "original" dataset, which is set based on what the api returns for the current filter... |
…id in history This adds a `sub_items` array to history items when they are fetched in the `historyItemsStore`, so that if any history item has other related items with the same hid, they are pushed to this array, and can be shown in the history. _Using an incomplete `COMPRESSED_EXTENSIONS` array here, there is probably a better way of confirming a dataset is compressed versus the original dataset (maybe using the backend?)_ Fixes galaxyproject#17220
…id in history This adds a `sub_items` array to history items when they are fetched in the `historyItemsStore`, so that if any history item has other related items with the same hid, they are pushed to this array, and can be shown in the history. _Using an incomplete `COMPRESSED_EXTENSIONS` array here, there is probably a better way of confirming a dataset is compressed versus the original dataset (maybe using the backend?)_ Fixes galaxyproject#17220
Thank you for fixing this @ahmedhamidawan ❤️ |
Describe the bug
We got a support request from a user, that ran out of storage and can not delete 2 large datasets, because they are not shown in the history (independent of the filter combinations).
In the storage manager, the datasets are listed and you can also find them in
User→Datasets
, but when you then click onview in history
the datasets will not appear (filters:deleted:any visible:any hid:61
).However, what appears is the compressed version, which has the same hid.
When I looked the datasets up in our database using
The datasets showed up as follows:
Galaxy Version and/or server at which you observed the bug
Galaxy Version: 23.1_europe
Commit: 5af8ba0
To Reproduce
Steps to reproduce the behavior:
Not sure how
The user reported that two jobs were running and only one finished and the other one was paused due to using ~200% of disk quota.
Galaxy shows the following message in the paused job:
Expected behavior
Dataset shown in the history and can be deleted and purged;
the compressed and the uncompressed version is visible and the uncompressed version can be deleted.
Screenshots
The text was updated successfully, but these errors were encountered: