-
Notifications
You must be signed in to change notification settings - Fork 441
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
clair3 breaks galaxy due to discrepancy in all_fasta columns #6211
Comments
I would consider this a bug in galaxy (and Clair). |
We can't really do anything there in Galaxy, failing to boot is probably the correct thing to do. |
We could just fail to load the tool, like we do for xml parsing errors, etc. |
This is a server misconfiguration that might have a huge impact, this needs to be fixed, failing is the right thing to do. |
is all_fasta even the right table to use? wouldn't fasta_indexes be the correct one? |
Still don't get why this break on au and not eu? |
|
tools-iuc/tools/clair3/clair3.xml Line 20 in 6da96d8
yes, that's why |
I guess the idea was that all_fasta is more widely populated ? I have no particular problem with this, of course it would be a little faster to go with fasta indexes. |
so for sure all three versions of the tool that we have installed on .eu carry that faulty tool data table file with them, but the these tables are not listed in our installed data tables. |
this PR might be enough #6311 |
Galaxy Australia's staging server failed to restart this morning. This entry in the shed_tool_data_table_conf.xml
has the wrong columns in
columns
. Each other entry for all_fasta has<columns>value, dbkey, name, path</columns>
and galaxy would not start until this new entry was commented out.The text was updated successfully, but these errors were encountered: