Skip to content

Prevent confusing logs in init_elements

Erwan Rouchet requested to merge prevent-confusing-logs into master

When troubleshooting frontend#323 (closed), I looked at the logs of init_elements. The first line of the logs was:

[INFO] Listed 9172 elements applying type, best_class filters on corpus 6763d457-1973-49a6-9d30-9f04a66c3107

This was confusing as the logs indicated the best_class filter had been applied, but it actually had not. The code that filled self.filters to apply them later on in the API caused self.filters to hold {"best_class": None} when no best_class filter was defined from the command line.

Edited by Erwan Rouchet

Merge request reports