Lance Parsons wrote:
I'm running a local instance of Galaxy that has been working quite
well. However, I've recently run into a problem when importing
datasets from a data library into a history. The Size on Disk of
the history grows by the size of the imported dataset, however, the
new
Good catch, that does indeed seem to be the issue. And it only seems to
happen with my older data libraries.
I didn't see a bug report for this, but I'd be happy to file one and/or
take a stab at a fix if someone can point me in the right direction in
the code.
Lance
Nate Coraor wrote:
Ah, sorry, I just saw your note to Alex regarding the pieces of code to
check out. I'll start doing some digging and let you know if I find
anything out.
See line 1925 in lib/galaxy/web/controllers/library_common.py. Try
adding a bit of debugging to find out if hda.deleted == True when the
Lance Parsons wrote:
Good catch, that does indeed seem to be the issue. And it only
seems to happen with my older data libraries.
I didn't see a bug report for this, but I'd be happy to file one
and/or take a stab at a fix if someone can point me in the right
direction in the code.
Any
I believe I may have found the bug...
Line 258 of cleanup_datasets.py is the query for library_dataset_ids
when force_retry is set. While it correctly eliminates the the
app.model.LibraryDataset.table.c.purged == False from the where clause,
it incorrectly eliminates the
I'm running a local instance of Galaxy that has been working quite
well. However, I've recently run into a problem when importing datasets
from a data library into a history. The Size on Disk of the history
grows by the size of the imported dataset, however, the new dataset is
not visible
