Print error even if blast error message does not match pattern #160
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.
Fix for #155
Error message
Cause
While we weren't able to reproduce the issue, the error itself is triggered because we are parsing the output of
makeblastdb
and searching for particular patterns to extract an appropriate error message (re.findall('REF\|(.*?)\''
). Perhaps either STDERR ofmakeblastdb
was empty for the above issue, or different versions of blast print different messages. See below codestaramr/staramr/blast/JobHandler.py
Lines 287 to 290 in 6e8ded8
Solution
The fix works by defaulting to just printing the full STDERR of
makeblastdb
if we can't pull out a more specific error message (rather than crashing).