Change log level for non-found files during PDF indexing #9678
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.
The PDF indexer writes all non-found files in the log.
Example:
It further outputs the index path:
This is IMHO too much noise. It is required for debugging.
I think, the reason was that
log.txt
never containedDEBUG
lines. This is fixed in this PR.One can enable debug using
tinylog.properties
as follows:level@org.jabref.logic.autosaveandbackup.BackupManager = debug
See https://devdocs.jabref.org/code-howtos/logging.html for details. That howto was not that good, so this PR also refines that howto @calixtus .
CHANGELOG.md
described in a way that is understandable for the average user (if applicable)