-
Notifications
You must be signed in to change notification settings - Fork 594
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
Fixed debug log severity for read threading messages. #8419
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain to me what exactly the behavior was here?
@@ -396,7 +396,7 @@ List<Haplotype> findBestPaths(final Collection<T> graphs, final Map<T, AssemblyR | |||
resultSet.add(h); | |||
} | |||
|
|||
logger.log(debug ? Level.INFO : Level.OFF, () -> "Adding haplotype " + h.getCigar() + " from graph with kmer " + assemblyResult.getKmerSize()); | |||
logger.log(debug ? Level.INFO : Level.TRACE, () -> "Adding haplotype " + h.getCigar() + " from graph with kmer " + assemblyResult.getKmerSize()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the issue is that calling logger.log(Level.OFF, message) will print that message in every case if you turn the logger off? If thats true I actually want you to revert these to the way they were before they were recently refactored (which i reviewed and didn’t catch here)… replace them with the previous statements
if(debug) {
logger.info( "Not using kmer size of " + kmerSize + " in read threading assembler because reference contains non-unique kmers");
}
Can this be fixed before an upcoming release? |
@jamesemery Yeah - back to you with updates. |
* Fixed debug log severity for read threading messages.
No description provided.