virtool/virtool-cli

More informative logging when OTU has no taxid

Closed this issue · 1 comments

Look at the second line here:

Found isolate data for 404404
Could not find isolate data for None
Found isolate data for 463360

I believe this is due to the OTU having no taxid. Please provide more informative log line. For example, Could not retrieve isolate data for because no taxid is defined.

I actually had made it so OTUs with no taxid don't end up in the scheduler and are effectively skipped without any logging. This might actually be a result of some unsafe calls when fetching and handling the taxids.

If you would like to have these logged as well I can do that.