published histories do not load #17622
Assignees
Labels
Comments
|
I was not able to reproduce it locally, yet. I tried to track it down on sentry, it might be related to: Looking at the dataset states in the schema, it seems that |
|
I think We might have some broken/ancient data in database? Carl's comment on that method 🫣 galaxy/lib/galaxy/managers/histories.py Line 867 in bc0d075 |
|
Yes, #17475. I'll take a look. |
|
Hmm, so deleted isn't actually a valid state, at all , and instead a boolean column. We have a bunch of datasets from 2008 doing that, but also a few from february of this year: I wonder if the ones from february have been manually set to that state, do you have any recollection of that @natefoo ? |
|
Fixed this with |
mvdbeek
added
area/database
4 tasks
|
What do you mean by manual thing? Something other than the app modifying the db? |
|
yes |
|
I think we need to have data migrations (or something of that sort), so that other admins can apply such fixes to their instances. It's separate from db schema migrations. Also, that would document all such fixes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
getting 500 from
https://usegalaxy.org/api/histories?limit=25&offset=0&search=&sort_by=update_time&sort_desc=true&show_own=false&show_published=true&show_shared=falseGalaxy Version and/or server at which you observed the bug
Galaxy Version: Main 24.0
Commit: 8b44fde05fe0a2aab1fb7f7e164f2adf96ce2387
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: